update existing references to yarn dev to use yarn start instead

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>

docs/getting-started/config/database.md

@@ -111,7 +111,7 @@ If you opt for the second option of replacing the entire string, take care to no
 [Start the Backstage app](../index.md#2-run-the-backstage-app):
 
 ```shell
-yarn dev
+yarn start
 ```
 
 After the Backstage frontend launches, you should notice that nothing has changed. This is a good sign. If everything is setup correctly above, this means that the data is flowing from the demo data files directly into your database!

docs/getting-started/index.md

@@ -116,11 +116,11 @@ If this fails on the `yarn install` step, it's likely that you will need to inst
 
 ## 2. Run the Backstage app
 
-Your Backstage app is fully installed and ready to be run! Now that the installation is complete, you can go to the application directory and start the app using the `yarn dev` command. The `yarn dev` command will run both the frontend and backend as separate processes (named `[0]` and `[1]`) in the same window.
+Your Backstage app is fully installed and ready to be run! Now that the installation is complete, you can go to the application directory and start the app using the `yarn start` command. The `yarn start` command will run both the frontend and backend as separate processes (named `[0]` and `[1]`) in the same window.
 
 ```bash
 cd my-backstage-app # your app name
-yarn dev
+yarn start
 ```
 
 ![Screenshot of the command output, with the message web pack compiled successfully](../assets/getting-started/startup.png)

docs/getting-started/logging-in.md

@@ -16,7 +16,7 @@ You should have already [have a standalone app](./index.md) and completed the Gi
 
 ## 1. Login to Backstage
 
-Run your Backstage app with `yarn dev`. Navigate to `http://localhost:3000`.
+Run your Backstage app with `yarn start`. Navigate to `http://localhost:3000`.
 
 If you're not already logged in, you should see a login screen like this,