fix the build

Author: HarshCasper

src/content/docs/aws/services/eks.mdx

@@ -438,7 +438,7 @@ For instance, you might have multiple microservices, each following a common pat
 In such cases, path-based routing may not be ideal if you need the services to be accessible in a uniform manner.
 
 To address this requirement, we recommend utilizing host-based routing rules, as demonstrated in the example below:
-<!-- markdownlint-disable MD007 -->
+
 ```bash
 cat <<EOF | kubectl apply -f -
 apiVersion: networking.k8s.io/v1
@@ -471,7 +471,7 @@ spec:
               number: 80
 EOF
 ```
-<!-- markdownlint-enable MD007 -->
+
 The example defines routing rules for two local endpoints - the first rule points to a service `service-1` accessible under `/v1`, and the second rule points to a service `service-2` accessible under the same path `/v1`.
 
 In the provided example, we define routing rules for two local endpoints.

src/content/docs/aws/services/iot.mdx

@@ -67,10 +67,10 @@ This message will be pushed to all subscribers of this topic, including the one
 ## Authentication
 
 LocalStack IoT maintains its own root certificate authority which is regenerated at every run.
-The root CA certificate can be retrieved from <http://localhost.localstack.cloud:4566/_aws/iot/LocalStackIoTRootCA.pem>.
+The root CA certificate can be retrieved from [`http://localhost.localstack.cloud:4566/_aws/iot/LocalStackIoTRootCA.pem`](http://localhost.localstack.cloud:4566/_aws/iot/LocalStackIoTRootCA.pem).
 
 :::note
-AWS provides its root CA certificate at <https://www.amazontrust.com/repository/AmazonRootCA1.pem>.
+AWS provides its root CA certificate at [`https://www.amazontrust.com/repository/AmazonRootCA1.pem`](https://www.amazontrust.com/repository/AmazonRootCA1.pem).
 [This section](https://docs.aws.amazon.com/iot/latest/developerguide/server-authentication.html#server-authentication-certs) contains information about CA certificates.
 :::
 

src/content/docs/aws/services/neptune.mdx

@@ -267,20 +267,19 @@ Gremlin transactions can be enabled by setting the environment `NEPTUNE_ENABLE_T
 Be aware that the `engine_version` provided when creating your cluster will be ignored and LocalStack will use `3.7.2` Gremlin Server.
 This feature is in beta and any feedback is appreciated.
 
-#### Current Limitations
-
-- Fixed id
-  - Creating a Vertex with an id in a transaction, then deleting it.
-    Trying to recreate a vertex with the same id will fail.
-- Serializer considerations
-  - While it is possible to connect to the server with a lower version of Gremlin Language Variants, there are breaking changes to the default `GraphBinarySerializersV1` serializer used by most languages.
-    One possible fix is to use the matching version for your language variant.
-    Otherwise, using the `GraphSONSerializersV3d0` serializer also seems to be working.
-    See example below.
-  - If using Neptune <= `1.2.0.2`, the Gryo message serializer is no longer supported.
-    Only affects users explicitly using that serializer.
-
-Example using `gremlinpython==3.6.2`
+## Current Limitations
+
+### Fixed ID
+
+-   If you create a vertex with an ID inside a transaction and then delete it, creating another vertex with the same ID will fail.
+    
+### Serializer
+
+-   You can connect using older Gremlin Language Variants, but `GraphBinarySerializersV1` has breaking changes.
+-   To fix this, either use the serializer version that matches your Gremlin variant, or switch to `GraphSONSerializersV3d0`, which works.
+-   If using Neptune version `1.2.0.2` or earlier, the Gryo serializer is no longer supported. This only affects users who explicitly use it.
+
+Here is an example of how to use the `GraphSONSerializersV3d0` serializer with `gremlinpython==3.6.2`:
 
 ```python
 from gremlin_python.driver import serializer

src/content/docs/aws/services/secretsmanager.mdx

@@ -175,8 +175,7 @@ The LocalStack Web Application provides a Resource Browser for managing secrets
 You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the **Resources** section, and then clicking on **Secrets Manager** under the **Security Identity Compliance** section.
 
 ![Secrets Manager Resource Browser](/images/aws/secrets-manager-resource-browser.png)
-<br>
-<br>
+
 The Resource Browser allows you to perform the following actions:
 
 - **Create Secret**: Create a new secret by clicking **Add a Secret** and providing the required details, such as Name, Tags, Kms Key Id, Secret String, and more.

src/content/docs/aws/services/sns.mdx

@@ -143,6 +143,7 @@ awslocal sqs receive-message \
 
 The following output is displayed:
 
+```bash
 {
     "Messages": [
         {
@@ -215,8 +216,6 @@ You can also call `DELETE /_aws/sns/platform-endpoint-messages` to clear the mes
 | `platform_endpoint_messages` | Contains endpoints ARN as field names. Each endpoint will have its messages in an Array. |
 | `region` | The region of the endpoints and messages. |
 
-<br>
-
 In this example, we will create a platform endpoint in SNS and publish a message to it.
 Run the following commands to create a platform endpoint:
 
@@ -339,8 +338,6 @@ You can also call `DELETE /_aws/sns/sms-messages` to clear the messages.
 | `sms_messages` | Contains phone numbers as field names. Each phone number will have its messages in an Array. |
 | `region` | The region from where the messages were sent. |
 
-<br>
-
 In this example, we will publish a message to a phone number and retrieve it:
 
 Publish a message to a phone number:
@@ -438,8 +435,6 @@ You can access the subscription tokens in JSON format through `GET /_aws/sns/sub
 | `subscription_token` | The Subscription token to be used with `ConfirmSubscription`. |
 | `subscription_arn` | The Subscription ARN provided. |
 
-<br>
-
 In this example, we will subscribe to an external SNS integration not confirming the subscription, retrieve the subscription token and manually confirm it:
 
 Create an SNS topic, and create a subscription to a external HTTP SNS integration:

src/content/docs/aws/services/sqs.mdx

@@ -161,7 +161,7 @@ awslocal sqs send-message \
 
 Receive the message twice to provoke a move into the dead-letter queue:
 
-```bas
+```bash
 awslocal sqs receive-message \
     --visibility-timeout 0 \
     --queue-url http://sqs.us-east-1.localhost.localstack.cloud:4566/000000000000/input-queue