Fix format errors and other small changes per suggestion

Signed-off-by: Sean Tan <seant@splunk.com>

docs/integrations/aws-s3/locations.md

@@ -15,26 +15,28 @@ plugin.
 
 ## Configuration
 
-To use this integration, add configuration to your root `app-config.yaml`:
+To use this integration, add configuration to your `app-config.yaml`:
 
 ```yaml
-awsS3:
-  - host: amazonaws.com
-    accessKeyId: ${AWS_ACCESS_KEY_ID}
-    secretAccessKey: ${AWS_SECRET_ACCESS_KEY}
+integrations:
+  awsS3:
+    - host: amazonaws.com
+      accessKeyId: ${AWS_ACCESS_KEY_ID}
+      secretAccessKey: ${AWS_SECRET_ACCESS_KEY}
 ```
 
 Then make sure the environment variables `AWS_ACCESS_KEY_ID` and
 `AWS_SECRET_ACCESS_KEY` are set when you run Backstage.
 
 Users with multiple AWS accounts may want to use a role for S3 storage that is
-in a different AWS account. Using the roleArn parameter as seen below, you can
+in a different AWS account. Using the `roleArn` parameter as seen below, you can
 instruct the AWS S3 reader to assume a role before accessing S3:
 
 ```yaml
-awsS3:
-  - host: amazonaws.com
-    accessKeyId: ${AWS_ACCESS_KEY_ID}
-    secretAccessKey: ${AWS_SECRET_ACCESS_KEY}
-    roleArn: 'arn:aws:iam::xxxxxxxxxxxx:role/example-role'
+integrations:
+  awsS3:
+    - host: amazonaws.com
+      accessKeyId: ${AWS_ACCESS_KEY_ID}
+      secretAccessKey: ${AWS_SECRET_ACCESS_KEY}
+      roleArn: 'arn:aws:iam::xxxxxxxxxxxx:role/example-role'
 ```