diff --git a/content/learn/quick-start/getting-started/apps/_index.md b/content/learn/quick-start/getting-started/apps/_index.md
index c72714b128..9f6e6e197b 100644
--- a/content/learn/quick-start/getting-started/apps/_index.md
+++ b/content/learn/quick-start/getting-started/apps/_index.md
@@ -25,4 +25,3 @@ cargo run
 
 in your project folder. You will notice that ... nothing happens. This is because we haven't told our app to do anything yet! Apps are just empty shells capable of running our application logic. Let's add some logic to our App using Bevy ECS.
 
-[`App`]: https://docs.rs/bevy/latest/bevy/app/struct.App.html
diff --git a/content/news/2020-08-10-introducing-bevy/index.md b/content/news/2020-08-10-introducing-bevy/index.md
index 3183d70d17..6c210b7289 100644
--- a/content/news/2020-08-10-introducing-bevy/index.md
+++ b/content/news/2020-08-10-introducing-bevy/index.md
@@ -82,7 +82,6 @@ fn main() {
 
 [`AddDefaultPlugins::add_default_plugins`] adds all of the features you probably expect from a game engine: a 2D / 3D renderer, asset loading, a UI system, windows, input, etc
 
-
 You can also register the default [`Plugins`] manually like this:
 
 ```rs
@@ -887,7 +886,6 @@ fn read_texture_system(textures: Res<Assets<Texture>>, texture_handle: &Handle<T
 
 ### Asset Events
 
-
 The `Assets<T>` collection is basically just a map from `Handle<T>` to `T` that records created, modified, and removed [`Events`]. These events can also be consumed as a system resource, just like any other [`Events`]:
 
 ```rs