From 4df195f5910e1edf0bebd0f22d61d951c5340a07 Mon Sep 17 00:00:00 2001 From: VewDev Date: Mon, 4 May 2026 12:33:27 +0200 Subject: [PATCH 1/5] fix: weird phrasing in Provide Feedback section of how_to_contribute --- organization/how_to_contribute.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/organization/how_to_contribute.rst b/organization/how_to_contribute.rst index 7df60df..e7909d2 100644 --- a/organization/how_to_contribute.rst +++ b/organization/how_to_contribute.rst @@ -39,9 +39,9 @@ Provide feedback ---------------- - **Report bugs & other issues** - As active users of the engine, you are better equipped to identify bugs and other issues than anyone else. + As active users of the engine, you are the most equipped to identify bugs and issues. To let us know about your findings, fill out this `bug report form `_ on our GitHub. - Make sure to include as much information as possible to ensure these issues can easily be reproduced by others. + Make sure to include as much information as possible to ensure these issues can easily be reproduced by contributors. - **Propose and discuss ideas** To meaningfully improve Godot, we first need the community to propose and discuss ideas to improve the engine. @@ -49,8 +49,7 @@ Provide feedback - **Test development versions** While it is recommended to use the stable releases for your projects, you can :ref:`help us test ` - dev releases, betas, and release candidates by opening a copy of your project in them and checking what problems this - might introduce or maybe even solves. Make sure to have a backup ready, to avoid potential irreversible changes. + development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems get solved. It is strongly recommended to backup your project before opening it in a development version to avoid potential irreversible changes in your project. Find recent `development versions `_ directly on our download page, or linked in their own blog posts. From adc5cb7055e385181fa826ceef1a7970ee33f2b3 Mon Sep 17 00:00:00 2001 From: VewDev Date: Mon, 4 May 2026 14:15:25 +0200 Subject: [PATCH 2/5] change "the most equipped" to "well equipped" --- organization/how_to_contribute.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/organization/how_to_contribute.rst b/organization/how_to_contribute.rst index e7909d2..5539a7b 100644 --- a/organization/how_to_contribute.rst +++ b/organization/how_to_contribute.rst @@ -39,7 +39,7 @@ Provide feedback ---------------- - **Report bugs & other issues** - As active users of the engine, you are the most equipped to identify bugs and issues. + As active users of the engine, you are well equipped to identify bugs and issues. To let us know about your findings, fill out this `bug report form `_ on our GitHub. Make sure to include as much information as possible to ensure these issues can easily be reproduced by contributors. From a6abe53ff91fc970f70e9b00b6b0b87b5ece0509 Mon Sep 17 00:00:00 2001 From: VewDev Date: Mon, 4 May 2026 15:27:55 +0200 Subject: [PATCH 3/5] address issues raised by athousandships --- organization/how_to_contribute.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/organization/how_to_contribute.rst b/organization/how_to_contribute.rst index 5539a7b..e39cdaf 100644 --- a/organization/how_to_contribute.rst +++ b/organization/how_to_contribute.rst @@ -41,7 +41,7 @@ Provide feedback - **Report bugs & other issues** As active users of the engine, you are well equipped to identify bugs and issues. To let us know about your findings, fill out this `bug report form `_ on our GitHub. - Make sure to include as much information as possible to ensure these issues can easily be reproduced by contributors. + Make sure to include as much information as possible to ensure these issues can easily be reproduced by others. - **Propose and discuss ideas** To meaningfully improve Godot, we first need the community to propose and discuss ideas to improve the engine. @@ -49,7 +49,7 @@ Provide feedback - **Test development versions** While it is recommended to use the stable releases for your projects, you can :ref:`help us test ` - development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems get solved. It is strongly recommended to backup your project before opening it in a development version to avoid potential irreversible changes in your project. + development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems are solved. It is strongly recommended to back up your project before opening it in a development version to avoid potential irreversible changes in your project. Find recent `development versions `_ directly on our download page, or linked in their own blog posts. From b45e7cef8a299729d7555af93e49254afaf4948f Mon Sep 17 00:00:00 2001 From: VewDev Date: Mon, 4 May 2026 15:59:38 +0200 Subject: [PATCH 4/5] separate backup recommendation to different line --- organization/how_to_contribute.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/organization/how_to_contribute.rst b/organization/how_to_contribute.rst index e39cdaf..c497884 100644 --- a/organization/how_to_contribute.rst +++ b/organization/how_to_contribute.rst @@ -49,7 +49,9 @@ Provide feedback - **Test development versions** While it is recommended to use the stable releases for your projects, you can :ref:`help us test ` - development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems are solved. It is strongly recommended to back up your project before opening it in a development version to avoid potential irreversible changes in your project. + development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems are solved. + + It is strongly recommended to back up your project before opening it in a development version to avoid potential irreversible changes in your project. Find recent `development versions `_ directly on our download page, or linked in their own blog posts. From e1dadf824b30f3a4a96185e63b0ff812df495e58 Mon Sep 17 00:00:00 2001 From: VewDev Date: Mon, 4 May 2026 16:05:50 +0200 Subject: [PATCH 5/5] only split line in source, not diff paragraph --- organization/how_to_contribute.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/organization/how_to_contribute.rst b/organization/how_to_contribute.rst index c497884..aec93e0 100644 --- a/organization/how_to_contribute.rst +++ b/organization/how_to_contribute.rst @@ -50,7 +50,6 @@ Provide feedback - **Test development versions** While it is recommended to use the stable releases for your projects, you can :ref:`help us test ` development releases, betas, and release candidates. You can open a copy of your project in the development versions and check if any new problems are created, and what problems are solved. - It is strongly recommended to back up your project before opening it in a development version to avoid potential irreversible changes in your project. Find recent `development versions `_ directly on our download page, or linked in their own blog posts.