revamp config docs

Author: HarshCasper

src/content/docs/aws/services/config.md

@@ -1,6 +1,5 @@
 ---
 title: "Config"
-linkTitle: "Config"
 description: Get started with Config on LocalStack
 persistence: supported
 tags: ["Free"]
@@ -13,7 +12,7 @@ Config provides a comprehensive view of the resource configuration across your A
 Config continuously records configuration changes and allows you to retain a historical record of these changes.
 
 LocalStack allows you to use the Config APIs in your local environment to assesses resource configurations and notifies you of any non-compliant items to mitigate potential security risks.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_config" >}}), which provides information on the extent of Config's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of Config's integration with LocalStack.
 
 ## Getting started
 
@@ -28,20 +27,20 @@ The S3 bucket will be used to receive a configuration snapshot on request and co
 The SNS topic will be used to notify you when a configuration snapshot is available.
 You can create a new S3 bucket and SNS topic using the AWS CLI:
 
-{{< command >}}
-$ awslocal s3 mb s3://config-test
-$ awslocal sns create-topic --name config-test-topic
-{{< /command >}}
+```bash
+awslocal s3 mb s3://config-test
+awslocal sns create-topic --name config-test-topic
+```
 
 ### Create a new configuration recorder
 
 You can now create a new configuration recorder to record configuration changes for specified resource types, using the [`PutConfigurationRecorder`](https://docs.aws.amazon.com/config/latest/APIReference/API_PutConfigurationRecorder.html) API.
 Run the following command to create a new configuration recorder:
 
-{{< command >}}
-$ awslocal configservice put-configuration-recorder \
+```bash
+awslocal configservice put-configuration-recorder \
     --configuration-recorder name=default,roleARN=arn:aws:iam::000000000000:role/config-role
-{{< /command >}}
+```
 
 We have specified the `roleARN` parameter to grant the configuration recorder the needful permissions to access the S3 bucket and SNS topic.
 In LocalStack, IAM roles are not enforced, so you can specify any role ARN you like.
@@ -68,8 +67,8 @@ You can inline the JSON into the `awslocal` command.
 
 Run the following command to create the delivery channel:
 
-{{< command >}}
-$ awslocal configservice put-delivery-channel \
+```bash
+awslocal configservice put-delivery-channel \
     --delivery-channel '{
     "name": "default",
     "s3BucketName": "config-test",
@@ -78,25 +77,25 @@ $ awslocal configservice put-delivery-channel \
         "deliveryFrequency": "Twelve_Hours"
     }
 }'
-{{< /command >}}
+```
 
 ### Start the configuration recorder
 
 You can now start recording configurations of the local AWS resources you have selected to record in your running LocalStack container.
 You can use the [`StartConfigurationRecorder`](https://docs.aws.amazon.com/config/latest/APIReference/API_StartConfigurationRecorder.html) API to start the configuration recorder.
 Run the following command to start the configuration recorder:
 
-{{< command >}}
-$ awslocal configservice start-configuration-recorder \
+```bash
+awslocal configservice start-configuration-recorder \
     --configuration-recorder-name default
-{{< /command >}}
+```
 
 You can list the delivery channels and configuration recorders using the [`DescribeDeliveryChannels`](https://docs.aws.amazon.com/config/latest/APIReference/API_DescribeDeliveryChannels.html) and [`DescribeConfigurationRecorderStatus`](https://docs.aws.amazon.com/config/latest/APIReference/API_DescribeConfigurationRecorderStatus.html) APIs respectively.
 
-{{< command >}}
-$ awslocal configservice describe-delivery-channels
-$ awslocal configservice describe-configuration-recorder-status
-{{< /command >}}
+```bash
+awslocal configservice describe-delivery-channels
+awslocal configservice describe-configuration-recorder-status
+```
 
 ## Current Limitations