sandbox env additional callouts

Author: AnilMaktala

src/pages/[platform]/deploy-and-host/sandbox-environments/setup/index.mdx

@@ -33,13 +33,10 @@ You can use a personal cloud sandbox environment that provides an isolated devel
 
 <Callout>
 
-Cloud sandbox environments are not intended for production workloads.
-
-DynamoDB GSI operations are long-running. Therefore in a sandbox, when a customer deletes or modifies an index on a DynamoDB table, we drop the table and recreate it rather than modifying the GSI.
-
-Where supported, we use CDK hot swapping to speed deployment of resources such as Lambda functions and AppSync resolver templates.
-
-When the customer makes an unsupported change to their Cognito User Pool (e.g., deleting a required field), we drop the user pool and recreate it.
+- **Cloud sandbox environments** are intended for development purposes and are not designed for production workloads.  
+- **DynamoDB GSI operations** are time-consuming, so when you delete or modify an index in a sandbox, Amplify drops and recreates the table instead of modifying the GSI.  
+- **CDK hot swapping** is used where supported to accelerate the deployment of resources such as Lambda functions and AppSync resolver templates.  
+- **Cognito User Pool changes:** If you make an unsupported change, such as deleting a required field, Amplify drops and recreates the user pool in the sandbox environment.
 
 </Callout>