fixed my dumbass mistake, wrote lineNumbers instead of showLineNumbers

Author: quetzalliwrites

src/content/docs/aws/capabilities/chaos-engineering/chaos-api.md

@@ -49,7 +49,7 @@ When active, rules are evaluated sequentially on every request to LocalStack unt
 
 The schema for the configuration is as follows.
 
-```json showLineNumbers
+```json showshowLineNumbers
 [
     {
         "region": "(str) Region name, e.g. 'ap-south-1'. If omitted, all regions are affected.",

src/content/docs/aws/capabilities/config/podman.md

@@ -101,7 +101,7 @@ podman machine set --rootful
 For the Docker Compose setup, use the following configuration.
 When running in rootless mode, ensure to comment out the HTTPS gateway port, as it is unable to bind to privileged ports below 1024.
 
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"

src/content/docs/aws/capabilities/networking/accessing-endpoint-url.mdx

@@ -130,7 +130,7 @@ docker run --rm -it --dns 172.27.0.2 --network ls <arguments> <image name>
 ```
 </TabItem>
 <TabItem label="docker-compose.yml">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"
@@ -200,7 +200,7 @@ docker run --rm it --network my-network <image name>
 ```
 </TabItem>
 <TabItem label="docker-compose.yml">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     # other configuration here

src/content/docs/aws/capabilities/networking/external-port-range.mdx

@@ -52,7 +52,7 @@ GATEWAY_LISTEN=0.0.0.0:4766 EXTERNAL_SERVICE_PORTS_START=4710 EXTERNAL_SERVICE_P
 ```
   </TabItem>
   <TabItem label="docker-compose">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack-main-1:
     container_name: localstack-main-1

src/content/docs/aws/capabilities/security-testing/custom-tls-certificates.mdx

@@ -34,7 +34,7 @@ If you run LocalStack in a docker container (which includes using [the CLI](/aws
 
 Create a `Dockerfile` containing the following commands:
 
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 FROM localstack/localstack:latest
 # or if using the pro image:
 FROM localstack/localstack-pro:latest
@@ -74,7 +74,7 @@ docker run <docker arguments> <image name>
 ```
 </TabItem>
 <TabItem label="docker-compose.yml">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     image: <image name>

src/content/docs/aws/capabilities/security-testing/explainable-iam.md

@@ -28,7 +28,7 @@ However we have not included the `iam:PassRole` permission, and we will use the
 
 Create a policy document named `policy_1.json` and add the following content:
 
-```json showLineNumbers
+```json showshowLineNumbers
 {
   "Version": "2012-10-17",
   "Statement": [
@@ -113,7 +113,7 @@ You can incorporate this action into the policy.
 For illustrative purposes, we will keep the example straightforward, using the same wildcard resource.
 Edit the `policy_1.json` file to include the `iam:PassRole` action:
 
-```json showLineNumbers
+```json showshowLineNumbers
 {
   "Version": "2012-10-17",
   "Statement": [

src/content/docs/aws/capabilities/security-testing/iam-policy-stream.md

@@ -57,7 +57,7 @@ awslocal sns create-topic --name test-topic
 In the other tab, the required policy will be generated.
 This policy can then be attached to an IAM role, enabling it to create the resource.
 
-```bash showLineNumbers
+```bash showshowLineNumbers
 Attached to identity: "arn:aws:iam::000000000000:root"
 
 Policy:

src/content/docs/aws/capabilities/state-management/cloud-pods.mdx

@@ -298,7 +298,7 @@ AUTO_LOAD_POD=foo-pod localstack start
 ```
 </TabItem>
 <TabItem label="Docker Compose">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     container_name: "localstack-main"
@@ -352,7 +352,7 @@ LocalStack, upon mounting `init-pods.d` to the appropriate location, will sequen
 
 The docker compose file for correctly mounting `init-pods.d` will look like:
 
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     container_name: "localstack-main"
@@ -498,7 +498,7 @@ With such a configuration, the `foo-pod` Cloud Pod will be loaded from the `bar-
 To properly configure the remote, you need to provide the needed environment variables when starting the LocalStack container.
 For instance, a S3 remote needs a `AWS_ACCESS_KEY` and a `AWS_SECRET_ACCESS_KEY`, as follows:
 
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 services:
   localstack:
     container_name: "localstack-main"

src/content/docs/aws/capabilities/state-management/persistence.mdx

@@ -28,7 +28,7 @@ PERSISTENCE=1 localstack start
 ```
 </TabItem>
 <TabItem label="Docker Compose">
-```yaml showLineNumbers
+```yaml showshowLineNumbers
 image: localstack/localstack-pro
 environment:
   - LOCALSTACK_AUTH_TOKEN=${LOCALSTACK_AUTH_TOKEN:?}

src/content/docs/aws/enterprise/k8s-operator.md

@@ -22,7 +22,7 @@ kubectl apply -f https://raw.githubusercontent.com/localstack/localstack-k8s-ope
 
 You can then deploy a LocalStack instance by storing the following file content as `localstack.yml` and applying it against the cluster via `kubectl apply -f localstack.yml`.
 
-```bash showLineNumbers
+```bash showshowLineNumbers
 apiVersion: api.localstack.cloud/v1alpha1
 kind: LocalStack
 metadata: