diff --git a/docs/getting-started/deployment-helm.md b/docs/getting-started/deployment-helm.md
index 6caff796a0..c062ed3951 100644
--- a/docs/getting-started/deployment-helm.md
+++ b/docs/getting-started/deployment-helm.md
@@ -10,8 +10,8 @@ sidebar_label: Kubernetes and Helm
 An example Backstage app can be deployed in Kubernetes using the
 [Backstage Helm charts](https://github.com/spotify/backstage/tree/master/contrib/chart/backstage).
 
-First, choose a DNS name where Backstage will be hosted, and create a YAML file for
-your custom configuration.
+First, choose a DNS name where Backstage will be hosted, and create a YAML file
+for your custom configuration.
 
 ```yaml
 appConfig:
diff --git a/docs/overview/architecture-overview.md b/docs/overview/architecture-overview.md
index 98c93d5cf7..ee2d3c6097 100644
--- a/docs/overview/architecture-overview.md
+++ b/docs/overview/architecture-overview.md
@@ -158,19 +158,19 @@ https://circleci.com.
 
 ## Databases
 
-As we have seen, both the `lighthouse-audit-service` and `catalog-backend` require a
-database to work with.
+As we have seen, both the `lighthouse-audit-service` and `catalog-backend`
+require a database to work with.
 
-At the time of writing, the `lighthouse-audit-service` requires PostgreSQL to work
-with. The service catalog backend uses an in-memory Sqlite3 instance. This is a
-development-oriented setup and there are plans to support other databases in the
-future.
+At the time of writing, the `lighthouse-audit-service` requires PostgreSQL to
+work with. The service catalog backend uses an in-memory Sqlite3 instance. This
+is a development-oriented setup and there are plans to support other databases
+in the future.
 
 To learn more about the future of databases and Backstage, see the following
 GitHub issues.
 
-* [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/spotify/backstage/issues/1598)
-* [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/spotify/backstage/pull/1527#discussion_r450374145)
+- [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/spotify/backstage/issues/1598)
+- [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/spotify/backstage/pull/1527#discussion_r450374145)
 
 ## Containerization
 
diff --git a/docs/plugins/testing.md b/docs/plugins/testing.md
index ba0d63fae5..e60b5fa8b7 100644
--- a/docs/plugins/testing.md
+++ b/docs/plugins/testing.md
@@ -285,7 +285,7 @@ jest.mock('./MyApi'); // Instruct Jest to swap all future imports of './MyApi.js
 
 import MyApi from './MyApi'; // Will actually return the contents of the file in the __mocks__ folder now
 
-it ('loads data', (done) => {
+it('loads data', done => {
   MyApi.fetchSomethingFromServer().then(result => {
     expect(result).toBe('some result object simulating server data here');
     done();
diff --git a/docs/tutorials/journey.md b/docs/tutorials/journey.md
index 56c561045e..7627920a75 100644
--- a/docs/tutorials/journey.md
+++ b/docs/tutorials/journey.md
@@ -239,12 +239,12 @@ hits merge.
 # 8. Attack of the Clones
 
 Sam just released v1.8.4 of the plugin, and at this point it's so popular that a
-couple of other plugins have started depending on the `sam.wise/spotify-track-id`
-annotation. One such plugin being the `spotify-album-art` plugin that can
-display the album art of the theme tune as the background of the entity header.
-Sam thinks it's all pretty cool, but doesn't like that the annotation that was
-once an internal concern of the plugin is now becoming a standard in the
-community.
+couple of other plugins have started depending on the
+`sam.wise/spotify-track-id` annotation. One such plugin being the
+`spotify-album-art` plugin that can display the album art of the theme tune as
+the background of the entity header. Sam thinks it's all pretty cool, but
+doesn't like that the annotation that was once an internal concern of the plugin
+is now becoming a standard in the community.
 
 In order to standardize the annotation in Backstage, Sam submits a Pull Request
 to the Backstage Core repo. The request suggests a new well-known metadata