run prettier

docs/api/utility-apis.md

@@ -71,10 +71,9 @@ import {
   AlertApiForwarder,
   ErrorApiForwarder,
   ErrorAlerter,
-  ConfigApi
+  ConfigApi,
 } from '@backstage/core';
 
-
 const apis = (config: ConfigApi) => {
   const builder = ApiRegistry.builder();
 
@@ -84,7 +83,7 @@ const apis = (config: ConfigApi) => {
   // The error API uses the alert API to send error notifications to the user.
   builder.add(errorApiRef, new ErrorAlerter(alertApi, new ErrorApiForwarder()));
   return builder.build();
-}
+};
 
 const app = createApp({
   apis,

docs/dls/design.md

@@ -116,8 +116,8 @@ components. If you’d like to help build up our design system, you can also add
 components we’ve designed to the Storybook as well.
 
 **[Figma](https://www.figma.com/@backstage)** - we're stoked to be using Figma
-Community to share our design assets. You can duplicate our UI Kit
-and design your own plugin for Backstage.
+Community to share our design assets. You can duplicate our UI Kit and design
+your own plugin for Backstage.
 
 **[Discord](https://discord.gg/EBHEGzX)** - all design questions should be
 directed to the _#design_ channel.

docs/features/software-templates/extending/create-your-own-publisher.md

@@ -7,18 +7,18 @@ Publishers are responsible for pushing and storing the templated skeleton after
 the values have been templated by the `Templater`. See
 [Create your own templater](./create-your-own-templater.md) for more info.
 
-They receive a directory or location where the templater has sucessfully run
-and is now ready to store somewhere. They also are given some other options
-which are sent from the frontend, such as the `storePath` which is a string of
-where the frontend thinks we should save this templated folder.
+They receive a directory or location where the templater has sucessfully run and
+is now ready to store somewhere. They also are given some other options which
+are sent from the frontend, such as the `storePath` which is a string of where
+the frontend thinks we should save this templated folder.
 
 Currently we provide the following `publishers`:
 
 - `github`
 
 This publisher is passed through to the `createRouter` function of the
-`@spotify/plugin-scaffolder-backend`. Currently, only one publisher is supported,
-but PR's are always welcome.
+`@spotify/plugin-scaffolder-backend`. Currently, only one publisher is
+supported, but PR's are always welcome.
 
 An full example backend can be found
 [here](https://github.com/spotify/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),

docs/features/software-templates/index.md

@@ -4,7 +4,7 @@ title: Software Templates
 ---
 
 The Software Templates part of Backstage is a tool that can help you create
-Components inside Backstage. By default, it  has the ability to load skeletons of
+Components inside Backstage. By default, it has the ability to load skeletons of
 code, template in some variables, and then publish the template to some location
 like GitHub.
 

docs/features/techdocs/creating-and-publishing.md

@@ -30,9 +30,9 @@ the documentation template.
 Create an entity from the documentation template and you will get the needed
 setup for free.
 
-!!! warning Currently the Backstage Software Templates are limited to create repositories
-inside GitHub organizations. You also need to generate an personal access token
-and use as an environment variable. Read more about this
+!!! warning Currently the Backstage Software Templates are limited to create
+repositories inside GitHub organizations. You also need to generate an personal
+access token and use as an environment variable. Read more about this
 [here](../software-templates/installation.md#runtime-dependencies).
 
 ### Manually add documentation setup to already existing repository

docs/getting-started/index.md

@@ -4,7 +4,8 @@ title: Running Backstage Locally
 ---
 
 First make sure you are using NodeJS with an Active LTS Release, currently v12.
-This is made easy with a version manager such as nvm which allows for version switching.
+This is made easy with a version manager such as nvm which allows for version
+switching.
 
 ```bash
 # Checking your version