Fix some lints in the new book (#2212)

Author: alice-i-cecile

content/learn/book/storing-data/entities-components.md

@@ -234,4 +234,3 @@ Over time, the Bevy community has converged on a few standard pieces of advice f
 [`Deref`]: https://doc.rust-lang.org/std/ops/trait.Deref.html
 [`DerefMut`]: https://doc.rust-lang.org/std/ops/trait.DerefMut.html
 [newtypes]: https://doc.rust-lang.org/rust-by-example/generics/new_types.html
-[struct update syntax]: https://doc.rust-lang.org/book/ch05-01-defining-structs.html#creating-instances-from-other-instances-with-struct-update-syntax

content/learn/book/storing-data/queries.md

@@ -123,6 +123,8 @@ while `&mut` is for mutable references, making it easy to remember the syntax on
 Let's take a look at how that might look in practice:
 
 ```rust,hide_lines=1-2
+# use bevy::prelude::*;
+#
 #[derive(Component)]
 struct Poisoned;
 

content/learn/book/storing-data/world.md

@@ -5,11 +5,12 @@ insert_anchor_links = "right"
 weight = 3
 +++
 
-The [`World`] is a catch-all container for *stuff*. 
+The [`World`] is a catch-all container for *stuff*.
 Entities, components, resources, assets -- all of these exist within a world.
 It's where your data lives.
 
 ## The World as a Database
+
 If you are familiar with SQL database terminology, you can think of a world as a database.
 Just like a database, a world contains several tables called **Archetypes**.
 Each [entity] is an entry within this database, stored as a row in on one of the archetype tables.
@@ -18,6 +19,7 @@ This allows archetype tables to be stored as dense arrays, containing only entit
 However, it also means that entities must be moved between tables when components are added or removed.
 
 ## Using the World
+
 With a `&World` reference, you can read anything out of the ecs. And with a `&mut World`, you can write to it as well.
 
 [entity]: /learn/book/storing-data/entities-components