Made changes as per PR comments

website/docs/automation/controlplanes/ack/configure-application.md

@@ -57,9 +57,12 @@ To verify that the **Carts** module is in fact using the DynamoDB table we just
 
 ![Cart screenshot](./assets/cart-items-present.png)
 
-And navigating to the Items table in the DynamoDB console to *Explore table items* shows
+And to check if items are in the cart as well, run
+
+```bash
+aws dynamodb scan --table-name items
+```
 
-![DynamoDB screenshot](./assets/dynamodb-items-table.png)
 
 Congratulations! You've successfully created AWS Resources without leaving the confines of the Kubernetes API!
 

website/docs/automation/controlplanes/ack/how-it-works.md

@@ -8,10 +8,12 @@ Each ACK service controller is packaged into a separate container image that is
 In this section of the workshop, as we will be working with Amazon DynamoDB, the ACK controllers for DynamoDB has been pre-installed in the cluster, running as a deployment in its own Kubernetes namespace. To see what's under the hood, lets run the below.
 
 ```bash
-$ kubectl describe deployment ack-dynamodb -n ack-dynamodb -oyaml
+$ kubectl describe deployment ack-dynamodb -n ack-dynamodb
 ```
 
-The ```-oyaml``` flag simply extracts the full YAML manifest of the deployment definition instead of the formatted output. Feel free to run the ```describe``` command without the flag as well.
+:::info
+kubectl also contains useful `-oyaml` and `-ojson` flags which extract either the full YAML or JSON manifests of the deployment definition instead of the formatted output.
+:::
 
 This controller will watch for Kubernetes custom resources for DynamoDB such as `dynamodb.services.k8s.aws.Table` and will make API calls to the DynamoDB endpoint based on the configuration in these resources created. As resources are created, the controller will feed back status updates to the custom resources in the `Status` fields. For more information about the spec of the manifest, click [here](https://aws-controllers-k8s.github.io/community/reference/).
 

website/docs/automation/controlplanes/ack/provision-resources.md

@@ -22,7 +22,7 @@ $ eksctl create iamserviceaccount --name carts-ack \
   --namespace carts --cluster $EKS_CLUSTER_NAME \
   --role-name carts-dynamodb-role \
   --attach-policy-arn $DYNAMODB_POLICY_ARN --approve
-
+  
 2023-10-30 12:45:17 [ℹ]  1 iamserviceaccount (carts/carts-ack) was included (based on the include/exclude rules)
 2023-10-30 12:45:17 [!]  serviceaccounts that exist in Kubernetes will be excluded, use --override-existing-serviceaccounts to override
 2023-10-30 12:45:17 [ℹ]  1 task: {