Open StefanSalewski opened 1 day ago
One more tiny issue is
https://bevyengine.org/learn/quick-start/getting-started/ecs/
"It often makes sense to break datatypes up in to small pieces to encourage code reuse."
I am quite sure that it should be into, not "in to".
And on the same page we have
"Quick Note: "hello world!" might show up in a different order than it does below. This is because systems run in parallel by default whenever possible."
At least in German language this makes not much sense, because a single entity have no order. I assume it is the same in English. Better would be
""hello world!" might show up in a different position than it does below."
or
"The lines of text might show up in a different order than it does below."
And at https://bevyengine.org/learn/quick-start/getting-started/plugins/ please replace
To use them all you have to do is:
by
To use them, all you have to do is:
I recently started studying Bevy -- notice that I am not a English native speaker, so perhaps I just misunderstand a few points?
For me the most serious issue is at https://bevyengine.org/learn/quick-start/getting-started/apps/
Even when reading a second time, I have no idea what "docs linked" refers to exactly. Where is the link? What section of the docs? And "we find three fields: world, schedule, and runner." What fields? Fields in a struct? What struct?
A few other, minor issues:
https://bevyengine.org/learn/quick-start/getting-started/setup/
For better flow, I would suggest this text:
First, navigate to a folder where you want to create your new project. Then, run the following command to create a new directory containing our rust executable project, and move into it:
cargo new my_bevy_game cd my_bevy_game
Now type cargo run to build and execute your project.
The use of run ... run is awkward, and build and rebuild is swapped. Better is
Now type cargo run again. The Bevy dependencies should start building. This will take some time as you are essentially building THE WHOLE engine from scratch. You will only need to do a full build once. Every rebuild after this one will be fast!
The last tiny issue is at https://bevyengine.org/learn/quick-start/getting-started/apps/
For my feeling, the colon after run is wrong, because the sentence continues. And to avoid duplicate "run" terms, we might better use "then execute".