Skip to content

fix: weird phrasing in Provide Feedback section of how_to_contribute #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
VewDev wants to merge 5 commits into
base: main
Choose a base branch
from
Open

fix: weird phrasing in Provide Feedback section of how_to_contribute #86

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
4df195f
fix: weird phrasing in Provide Feedback section of how_to_contribute
VewDev May 4, 2026
adc5cb7
change "the most equipped" to "well equipped"
VewDev May 4, 2026
a6abe53
address issues raised by athousandships
VewDev May 4, 2026
b45e7ce
separate backup recommendation to different line
VewDev May 4, 2026
e1dadf8
only split line in source, not diff paragraph
VewDev May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions organization/how_to_contribute.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ 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 well equipped to identify bugs and issues.
To let us know about your findings, fill out this `bug report form <https://github.com/godotengine/godot/issues/new/choose>`_ on our GitHub.
Make sure to include as much information as possible to ensure these issues can easily be reproduced by others.

Expand All @@ -49,8 +49,8 @@ Provide feedback

- **Test development versions**
While it is recommended to use the stable releases for your projects, you can :ref:`help us test <doc_testing_development_versions>`
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 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 <https://godotengine.org/download/preview/>`_ directly on our download page, or linked in their own blog posts.

Expand Down