Fix Backstage case

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!