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,
 

docs/permissions/custom-rules.md

@@ -187,7 +187,7 @@ To install custom rules in a plugin, we need to use the [`PermissionsRegistrySer
    backend.add(import('./extensions/catalogPermissionRules'));
    ```
 
-5. Now when you run you Backstage instance - `yarn dev` - the rule will be added to the catalog plugin.
+5. Now when you run you Backstage instance - `yarn start` - the rule will be added to the catalog plugin.
 
 The updated policy will allow catalog entity resource permissions if any of the following are true:
 

docs/permissions/getting-started.md

@@ -103,10 +103,10 @@ Now lets test end to end that the permissions framework is setup and configured
      enabled: true
    ```
 
-2. Now run `yarn dev`, Backstage should load up in your browser
+2. Now run `yarn start`, Backstage should load up in your browser
 3. You should see that you have entities in your Catalog, pretty simple
 4. Let's change this line in our Test Permission Policy `return { result: AuthorizeResult.ALLOW };` to be `return { result: AuthorizeResult.DENY };`
-5. Run `yarn dev` once again, Backstage should load up in your browser
+5. Run `yarn start` once again, Backstage should load up in your browser
 6. This time you should not see any entities in your Catalog, if you do then something went wrong along the way and you'll need to review the steps above
 7. Revert the change we made in step 4 so that the line looks like this: `return { result: AuthorizeResult.ALLOW };`
 

docs/plugins/create-a-plugin.md

@@ -25,7 +25,7 @@ And then select `frontend-plugin`.
 This will create a new Backstage Plugin based on the ID that was provided. It
 will be built and added to the Backstage App automatically.
 
-> If the Backstage App is already running (with `yarn start` or `yarn dev`) you
+> If the Backstage App is already running (with `yarn start`) you
 > should be able to see the default page for your new plugin directly by
 > navigating to `http://localhost:3000/my-plugin`.
 

docs/plugins/integrating-search-into-plugins.md

@@ -245,7 +245,7 @@ You can also check out the documentation on [how to test Backstage plugin module
 
 #### 9. Running the collator locally
 
-Run `yarn dev` in the root folder of your Backstage project and look for logs like these:
+Run `yarn start` in the root folder of your Backstage project and look for logs like these:
 
 ```sh
 [backend]: YYYY-MM-DDTHH:MM:SS.000Z search info Task worker starting: search_index_faq_snippets, {"version":2,"cadence":"PT10M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} task=search_index_faq_snippets

docs/tooling/local-dev/debugging.md

@@ -19,7 +19,7 @@ Changing the level can be done by setting the `LOG_LEVEL` environment variable.
 For example, to turn on debug logs when running the app locally, you can run:
 
 ```shell
-LOG_LEVEL=debug yarn dev
+LOG_LEVEL=debug yarn start
 ```
 
 The resulting log should now have more information available for debugging:

docs/tooling/local-dev/profiling.md

@@ -60,6 +60,6 @@ See more command options in the AutoCannon documentation.
 Profiling the frontend can be done by using the `React DevTools` extension for Chrome or Firefox.
 The extension is available for download from the Chrome Web Store or the Firefox Add-ons website.
 
-To start profiling, start the application with `yarn dev` and open inspector in the browser. In the
+To start profiling, start the application with `yarn start` and open inspector in the browser. In the
 `Profiler` tab (far to the right), click the `Start profiling` button to start recording. After
 you have recorded some data by navigating through the page, click the `Stop profiling` button to stop the recording.

docs/tutorials/setup-opentelemetry.md

@@ -62,7 +62,7 @@ For local development, you can add the required flag in your `packages/backend/p
   ...
 ```
 
-You can now start your Backstage instance as usual, using `yarn dev`.
+You can now start your Backstage instance as usual, using `yarn start`.
 
 ## Production Setup