Text formatting (#53)

Author: sitole

docs/migration/v2.mdx

@@ -40,13 +40,14 @@ sandbox = Sandbox(template="base")
 
 ### 2. Secure communication by default
 
-Sandboxes are now **secure by default**. That means you cannot access the sandbox controller directly via its URL without authentication header.
-SDK handles authentication header for you automatically.
 
-For custom templates created before envd `v0.2.0`, you need to rebuild the templates to enable secure communication,
-otherwise you will receive error messages when creating sandboxes. You can check template envd version via `e2b template list` command or templates list in dashboard.
+Sandboxes are now **secure by default**. This means you can't access the sandbox controller directly through its URL without an authentication header.
+The SDK automatically handles the authentication header for you.
 
-You can temporarily disable secure communication by setting `secure` to `false` during sandbox creation, but this is not recommended for production use.
+For custom templates created before envd `v0.2.0`, you need to rebuild them to enable secure communication.
+Otherwise, you will receive error messages when creating sandboxes. You can check the template envd version using the `e2b template list` command or view the templates list in the dashboard.
+
+You can temporarily disable secure communication by setting `secure` to `false` during sandbox creation, but this is not recommended for production environments.
 
 <CodeGroup>
 ```js JavaScript & TypeScript

docs/sandbox/secured-access.mdx

@@ -5,39 +5,39 @@ sidebarTitle: Secured access
 
 Secure access authenticates communication between SDK and sandbox controller.
 
-Sandbox controller runs in sandbox itself and exposes APIs for work with file system, run command etc.
-Without using secured access, anyone with sandbox ID can access the controller APIs and control the sandbox from inside.
+Sandbox controller runs in sandbox itself and exposes APIs for work with file system, run commands, and generally control the sandbox via our SDK.
+Without secure access, anyone with a sandbox ID can access the controller APIs and control the sandbox from inside.
 
 <Note>
     SDKs version `v2.0.0` and above are using secure access by default when creating sandbox. This may not be compatible with older custom templates and you may need to rebuild them.
 </Note>
 
 ## Migration path
 
-When you are using custom templates created before envd `v0.2.0`, you need to rebuild the templates to enable secure access.
-Temporary, you can disable secure access by setting `secure` to `false` during sandbox creation, but this is not recommended for production use as it opens up security risks.
+When using custom templates created before envd `v0.2.0`, you need to rebuild the templates to enable secure access.
+Temporarily, you can disable secure access by setting `secure` to `false` during sandbox creation, but this is not recommended for production use because it increases security risks.
 
-You can check template envd version via `e2b template list` command or templates list in dashboard.
+You can check the template envd version using the `e2b template list` command or by viewing the templates list on the dashboard.
 
 ## Supported versions
 
-All sandboxes based on template with envd version at least `v0.2.0` already supports secure access without any additional changes.
+All sandboxes based on templates with envd version at least `v0.2.0` already support secure access without any additional changes.
 
-Secured access flag was introduced in `1.5.0` for JavaScript and Python SDKs to be used optionally.
-With SDKs version `v2.0.0` and above, sandboxes are created with secure access enabled by default.
+The secure access flag was introduced in `1.5.0` for JavaScript and Python SDKs to be used optionally.
+Starting with SDK version `v2.0.0`, sandboxes are created with secure access enabled by default.
 
 ## Access sandbox API directly
 
-In some cases you may want to access sandbox controller APIs directly via its URL, for example when you are not using SDKs.
-When secure access is enabled, you need to provide an authentication token that was returned during sandbox creation.
+In some cases, you might want to access sandbox controller APIs directly through its URL, such as when you are not using SDKs.
+When secure access is enabled, you must provide an authentication token that was returned during sandbox creation.
 
-Each call to sandbox controller must include an additional header `X-Access-Token` with access token value returned during sandbox creation.
+Each call to the sandbox controller must include an additional header `X-Access-Token` with the access token value returned during sandbox creation.
 
 For sandbox [upload](/docs/filesystem/upload#upload-with-pre-signed-url) and [download](/docs/filesystem/download#download-with-pre-signed-url) URLs, you need to generate pre-signed URLs. We are advising to use SDK for generating presigned URLs.
 
 ## Disable secure access
 
-Disabling secured access is not recommended as it opens up security risks.
+Disabling secured access is discouraged because it creates security vulnerabilities.
 
 <CodeGroup>
     ```js JavaScript & TypeScript