Merge pull request #7184 from adamdmharvey/doco-update

fix(docs): Update Docusaurus build errors & minor rewording

docs/deployment/docker.md

@@ -122,12 +122,12 @@ sometimes desired because Docker in Docker is not available in the build
 environment, or due to other requirements.
 
 The build is split into three different stages, where the first stage finds all
-of the `package.json`s that are relevant for the initial install step enabling
-us to cache the initial `yarn install` that installs all dependencies. The
-second stage executes the build itself, and is similar to the steps we execute
-on the host in the host build. The third and final stage then packages it all
-together into the final image, and is similar to the `Dockerfile` of the host
-build.
+of the `package.json` files that are relevant for the initial install step
+enabling us to cache the initial `yarn install` that installs all dependencies.
+The second stage executes the build itself, and is similar to the steps we
+execute on the host in the host build. The third and final stage then packages
+it all together into the final image, and is similar to the `Dockerfile` of the
+host build.
 
 The following `Dockerfile` executes the multi-stage build and should be added to
 the repo root:

docs/deployment/index.md

@@ -1,7 +1,7 @@
 ---
 id: index
 title: Deploying Backstage
-sidebar_title: Overview
+sidebar_label: Overview
 description: Packaging Backstage and deploying to production
 ---
 
@@ -32,7 +32,7 @@ requires the first two steps.
 An example of deploying Backstage with a [Helm chart](helm.md), a common pattern
 in AWS, is also available. There is also a contrib guide to deploying Backstage
 with
-[AWS Fargate and Aurora PostgreSQL](https://github.com/backstage/backstage/blob/master/contrib/docs/tutorials/aws-fargate-deployment.md)
+[AWS Fargate and Aurora PostgreSQL](https://github.com/backstage/backstage/blob/master/contrib/docs/tutorials/aws-fargate-deployment.md).
 
 Please consider contributing other deployment guides if you get Backstage set up
 on common infrastructure, it would be a great benefit to the community.

docs/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md

@@ -2,8 +2,7 @@
 id: migrating-from-v1alpha1-to-v1beta2
 title: Migrating to v1beta2 templates
 # prettier-ignore
-description:
-  How to move your old templates from v1alpha1 to the more declarative v1beta2
+description: How to move your old templates from v1alpha1 to the more declarative v1beta2
 ---
 
 # What's new?