docs: wording and structural changes to cloud (#12820)

* docs: wording and structural changes to cloud

* Fix vale error

* Fix faq title

* Fix heading levels

* Small change to previews

www/apps/cloud/app/s3/page.mdx

@@ -4,13 +4,13 @@ export const metadata = {
 
 # {metadata.title}
 
-In this guide, you'll learn about the managed S3 storage service that Cloud provides as part of your project environments.
+In this guide, you'll learn about the managed S3 storage service that Medusa provides as part of your project environments.
 
 ## Managed S3 Storage Service
 
-Cloud offers a managed S3 storage service for your project environments. Each environment has its own dedicated S3 bucket that is automatically provisioned when the environment is created.
+Medusa offers a managed S3 storage service for your project environments. Each environment has its own dedicated S3 bucket that is automatically provisioned when the environment is created.
 
-So, when you create a new project, Cloud creates a production S3 bucket for the production environment. If you create a staging environment, Cloud creates a separate S3 bucket for that environment as well.
+So, when you create a new project, Medusa creates a production S3 bucket for the production environment. If you create a staging environment, Medusa creates a separate S3 bucket for that environment as well.
 
 By default, the S3 bucket is private, but the files you upload to the bucket are publicly accessible. This is necessary for serving product images and other assets in your Medusa application.
 
@@ -20,19 +20,19 @@ By default, the S3 bucket is private, but the files you upload to the bucket are
 
 ## Configured S3 File Module Provider
 
-Cloud automatically configures your Medusa application to use the [S3 File Module Provider](!resources!/infrastructure-modules/file/s3).
+Medusa automatically configures your Medusa application to use the [S3 File Module Provider](!resources!/infrastructure-modules/file/s3).
 
 So, you don't need to configure the S3 File Module Provider or set up S3 manually. Also, if you have the S3 File Module Provider configured in `medusa-config.ts`, remove it to avoid conflicts.
 
 <Note>
 
-If you're using a Medusa version before v2.7.0, [contact support](../support/page.mdx) for assistance in configuring the S3 File Module Provider.
+If you're using a Medusa version before v2.7.0, contact support for assistance in configuring the S3 File Module Provider.
 
 </Note>
 
 ### Access S3 Configurations
 
-Since Cloud is a managed service, you can't directly access your S3 bucket or its configurations. Cloud also doesn't expose the S3 bucket connection or configuration details.
+Since Cloud is a managed service, you can't directly access your S3 bucket or its configurations. Medusa also doesn't expose the S3 bucket connection or configuration details.
 
 ### Override S3 Configurations
 
@@ -42,6 +42,6 @@ Then, configure the S3 File Module Provider in your `medusa-config.ts` file to c
 
 <Note title="Tip">
 
-To set the connection options of your external S3 instance, refer to the [Environments](../environments/page.mdx#add-environment-variables) guide to learn how to add environment variables. You can then use these variables in your `medusa-config.ts` file to connect to your S3 instance.
+To set the connection options of your external S3 instance, refer to the [Environments](../environments/environment-variables/page.mdx#add-environment-variables) guide to learn how to add environment variables. You can then use these variables in your `medusa-config.ts` file to connect to your S3 instance.
 
 </Note>