fix: devservices use local not LOCAL (#13631)

Author: krystofwoldrich

develop-docs/development-infrastructure/devservices.mdx

@@ -97,22 +97,22 @@ devservices toggle snuba
 or you can specify the runtime explicitly:
 
 ```shell
-devservices toggle snuba LOCAL
+devservices toggle snuba local
 ```
 
 This tells devservices to treat Snuba as a service that should be started alongside dependent services like Sentry. Dependencies of Snuba, such as Redis, Kafka, and Clickhouse, will still run as containers.
 
 <Alert title="Note">
-  Toggling to LOCAL does not start the dev server for that service. You'll need to start that manually.
+  Toggling to `local` does not start the dev server for that service. You'll need to start that manually.
 </Alert>
 
 ### What happens when you toggle
 
-If Sentry is already running, toggling Snuba to LOCAL will:
+If Sentry is already running, toggling Snuba to `local` will:
 1. Stop Snuba's containers (unless shared by another service)
 2. Start Snuba's non-local dependencies (Redis, Kafka, Clickhouse) as containers
 
-If Sentry is not yet running, the next time `devservices up` is run, Snuba (and any other services you toggle to LOCAL) will be automatically started as local services alongside Sentry.
+If Sentry is not yet running, the next time `devservices up` is run, Snuba (and any other services you toggle to `local`) will be automatically started as local services alongside Sentry.
 
 If you want to bring up Snuba, or other local runtime dependencies in a non-default mode, you can:
 1. Tell devservices to not bring them up automatically by passing the `--exclude-local` flag to `devservices up`.