diff --git a/docs/source/api/plugin/landing-pages.md b/docs/source/api/plugin/landing-pages.md
index 22c7535da2a..6a0fe23f496 100644
--- a/docs/source/api/plugin/landing-pages.md
+++ b/docs/source/api/plugin/landing-pages.md
@@ -14,7 +14,7 @@ This includes plugins for:
 * [Disabling the landing page entirely](#disabling-the-landing-page)
 
 These plugins work by implementing the [`renderLandingPage`](../../integrations/plugins-event-reference/#renderlandingpage) plugin event, which serves an HTML page whenever a browser includes an `accept: text/html` header. Aside from these, you can also create a  [custom plugin](../../integrations/plugins/) that renders a [custom landing page](../../testing/build-run-queries/#custom-landing-page).
- 
+
 ## Default behavior
 
 If you don't manually install any plugin that implements `renderLandingPage`, Apollo Server does the following by default:
@@ -223,7 +223,7 @@ This plugin takes the same arguments as the [`renderPlaygroundPage` function](ht
 </td>
 <td>
 
-By default, this plugin loads a specific npm version of `@apollographql/graphql-playground-react` from a CDN. The version is hard-coded in `apollo-server-core` and is typically incremented when new versions of the Playground fork are released (this is rare because the project is retired). 
+By default, this plugin loads a specific npm version of `@apollographql/graphql-playground-react` from a CDN. The version is hard-coded in `apollo-server-core` and is typically incremented when new versions of the Playground fork are released (this is rare because the project is retired).
 
 You can specify a different version here.