Merge branch 'main' into 160_flatten_book_layout

content/learn/book/contributing/_index.md

@@ -15,4 +15,4 @@ Bevy is built by volunteers. If you want to help us build the next great game en
 * If you are a software developer and you want to help out, check out the [Contributing Code](/learn/book/contributing/code) section.
 * If you are good at teaching or writing, consider [contributing to our docs](/learn/book/contributing/docs).
 
-We want Bevy to be a vibrant developer community ... thats actually why we chose the name! A Bevy is a group of birds, just like we are a group of game developers. Join the Bevy!
+We want Bevy to be a vibrant developer community ... that's actually why we chose the name! A Bevy is a group of birds, just like we are a group of game developers. Join the Bevy!

content/learn/book/getting-started/ecs.md

@@ -155,7 +155,7 @@ fn update_people(mut query: Query<&mut Name, With<Person>>) {
     for mut name in &mut query {
         if name.0 == "Elaina Proctor" {
             name.0 = "Elaina Hume".to_string();
-            break; // We break out of the loop here, because we don’t need to change any other names
+            break; // We don’t need to change any other names
         }
     }
 }
@@ -176,4 +176,5 @@ fn main() {
 
 Note that we have used `.chain()` on the two systems. This is because we want them two to run in exactly the order they're listed in the code: with `update_people` occurring before `greet_people`.
 If they weren’t, the name might change after we greet the people.
+
 But we don’t add the `hello_world` system to the chain, because it doesn’t matter when it runs. This way, Bevy can run `hello_world` in parallel while the other systems are running.

content/learn/book/introduction.md

@@ -35,7 +35,7 @@ For a more in-depth introduction, check out the [Introducing Bevy](/news/introdu
 
 Bevy is still in the early stages of development. Important features are missing. Documentation is sparse. A new version of Bevy containing breaking changes to the API is released [approximately once every 3 months](https://bevyengine.org/news/bevy-0-6/#the-train-release-schedule). We provide [migration guides](https://bevyengine.org/learn/book/migration-guides/), but we can't guarantee migrations will always be easy. Use only if you are willing to work in this environment.
 
-If you are currently trying to pick an engine for your Next Big Project™, we recommend that you check out [Godot Engine](https://godotengine.org). It is currently much more feature-complete and stable. And it is also free, open-source, and [scriptable with Rust](https://github.com/GodotNativeTools/godot-rust)!
+If you are currently trying to pick an engine for your Next Big Project™, we recommend that you check out [Godot Engine](https://godotengine.org). It is currently much more feature-complete and stable. And it is also free, open-source, and [scriptable with Rust](https://github.com/godot-rust/gdext)!
 
 This official book is still very incomplete. It will help you get started with the setup and learning the basics, but it does not yet cover most of Bevy's features. See the [Next Steps](/learn/book/next-steps/) page for links to other, more exhaustive, learning resources you can use.
 

templates/index.html

@@ -271,6 +271,9 @@ <h3 class="sponsors__amount">$100 / month</h3>
                 <a class="sponsors__link" href="https://wunder.software">
                     <img class="sponsors__logo" src="assets/Wunder_Software_GmbH.png" alt="Wunder Software GmbH logo" />
                 </a>
+                <a class="sponsors__link" href="https://basementfloodhelpers.com" >
+                    <img class="sponsors__logo" src="assets/BFH.png" alt="Basement Flood Helpers logo"/>
+                </a>
             </div>
         </div>
         <h2 class="past-sponsors-title">Past Sponsors</h2>