Fix Backstage case

docs/features/search/README.md

@@ -67,7 +67,7 @@ more to come...
 - As a contributor I should be able to integrate plugin data to the indexing
   process of Backstage Search by using the standardized API.
 - As a software engineer I should be able to search for all content (for
-  example, entities, metadata, documentation) in backstage search.
+  example, entities, metadata, documentation) in Backstage search.
 
 more to come...
 

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

@@ -86,7 +86,7 @@ follows:
 
 _note_ Currently the templaters that we provide are basically Docker action
 containers that are run on top of the skeleton folder. This keeps dependencies
-to a minimum for running backstage scaffolder, but you don't _have_ to use
+to a minimum for running Backstage scaffolder, but you don't _have_ to use
 Docker. You can `pip install cookiecutter` to run it locally in your backend.
 You could create your own templater that spins up an EC2 instance and downloads
 the folder and does everything using an AMI if you want. It's entirely up to

docs/features/software-templates/index.md

@@ -39,13 +39,13 @@ internally.
 ![Enter some variables](../../assets/software-templates/template-picked.png)
 
 After filling in these variables, you'll get some more fields to fill out which
-are required for backstage usage: the owner (which is a `user` in the backstage
+are required for Backstage usage: the owner (which is a `user` in the backstage
 system), the `storePath` (which right now must be a GitHub Organisation or
 GitHub user and a non-existing GitHub repository name in the format
 `organisation/reponame`), and a GitHub team or user account which should be
 granted admin access to the repository.
 
-![Enter backstage vars](../../assets/software-templates/template-picked-2.png)
+![Enter Backstage vars](../../assets/software-templates/template-picked-2.png)
 
 ### Run!
 

docs/getting-started/development-environment.md

@@ -31,7 +31,7 @@ $ yarn start
 This should open a local instance of Backstage in your browser, otherwise open
 one of the URLs printed in the terminal.
 
-By default, backstage will start on port 3000, however you can override this by
+By default, Backstage will start on port 3000, however you can override this by
 setting an environment variable `PORT` on your local machine. e.g.
 `export PORT=8080` then running `yarn start`. Or `PORT=8080 yarn start`.
 

docs/plugins/integrating-plugin-into-service-catalog.md

@@ -59,7 +59,7 @@ accordingly inside `Router.tsx`)
 ### Import and use router in the APP
 
 In the `app/src/components/catalog/EntityPage.tsx` (app === your folder,
-containing backstage app) import your created Router:
+containing Backstage app) import your created Router:
 
 ```tsx
 import { Router as MyPluginRouter } from '@backstage/plugin-my-plugin;

docs/reference/utility-apis/BackstageIdentityApi.md

@@ -79,7 +79,7 @@ Referenced by: [getBackstageIdentity](#getbackstageidentity).
 <pre>
 export type BackstageIdentity = {
   /**
-   * The backstage user ID.
+   * The Backstage user ID.
    */
   id: string;