Merge pull request #303 from codesandbox/fix/correct-typos-in-sdk-docs

fix: correct typos

Author: tristandubbeld

packages/projects-docs/pages/sdk/bootups.mdx

@@ -48,7 +48,7 @@ if (client.bootupType === 'CLEAN') {
 
 ## Agent updates
 
-Every Sandbox has an agent running on it. This agent is the what allows you to interact with the Sandbox environment.
+Every Sandbox has an agent running on it. This agent is what allows you to interact with the Sandbox environment.
 
 When a new version of the agent is published, existing sandboxes will need to restart before they get new version.
 

packages/projects-docs/pages/sdk/clients.mdx

@@ -1,6 +1,6 @@
 ---
 title: Clients
-description: Learn how to connect to a sandboxwith the CodeSandbox SDK.
+description: Learn how to connect to a sandbox with the CodeSandbox SDK.
 ---
 
 import { Callout } from 'nextra-theme-docs'

packages/projects-docs/pages/sdk/faq.mdx

@@ -29,7 +29,7 @@ Currently, we only allow changing the default specs for all VMs created with the
 
 ## Are VMs created by the SDK covered by any cybersecurity certifications?
 
-CodeSandbox and it's infrastructure, including VMs are SOC 2 Type II compliant. You can read our SOC 2 announcement on our [blog](https://codesandbox.io/blog/codesandbox-is-now-soc-2-compliant)
+CodeSandbox and its infrastructure, including VMs are SOC 2 Type II compliant. You can read our SOC 2 announcement on our [blog](https://codesandbox.io/blog/codesandbox-is-now-soc-2-compliant)
 
 ## Is it possible to self-host CodeSandbox SDK?
 

packages/projects-docs/pages/sdk/filesystem.mdx

@@ -16,7 +16,7 @@ operations are relative to the workspace directory of the sandbox (which is `/pr
 
 ### Writing & Reading Files
 
-You can read & write files using an api that's similer to the Node.js fs module:
+You can read & write files using an api that's similar to the Node.js fs module:
 
 ```ts
 // Writing text files

packages/projects-docs/pages/sdk/hosts.mdx

@@ -7,7 +7,7 @@ import { Callout } from 'nextra-theme-docs'
 
 # Hosts
 
-Hosts are the services exposed by your Sandbox. They all have their own hostname which includes the port. The `client.hosts` API will allow you to access these your Sandbox hosts securily using signed urls, headers or cookies.
+Hosts are the services exposed by your Sandbox. They all have their own hostname which includes the port. The `client.hosts` API will allow you to access your Sandbox hosts securely using signed urls, headers or cookies.
 
 The `hostToken` is embedded in your session.
 

packages/projects-docs/pages/sdk/interpreters.mdx

@@ -28,5 +28,5 @@ const pythonResult = await client.interpreters.python("'Hello from Python!'");
 These interpreters will automatically return the last expression as output, but you can print values to the console at any point for multiple outputs.
 
 <Callout>
-Note that the interpreters will not resolve until the interpretation resolves. We are open to changing this behavior if you have any feedback or suggestions! Or you can always wield your own by using commands.
+Note that the interpreters will not resolve until the interpretation resolves. We are open to changing this behavior if you have any feedback or suggestions! Or you can always implement your own by using commands.
 </Callout>

packages/projects-docs/pages/sdk/pricing.mdx

@@ -37,7 +37,7 @@ To pick the most suitable plan for your use case, consider how many concurrent V
 - Scale plan: 250 concurrent VMs
 - Enterprise plan: custom concurrent VMs
 
-In case you expect a a high volume of VM runtime, our Enterprise plan also provides special discounts on VM credits.
+In case you expect a high volume of VM runtime, our Enterprise plan also provides special discounts on VM credits.
 
 <Callout> If you're interested in an Enterprise plan please contact the [Together.ai Sales Team](https://www.together.ai/contact-sales)</Callout>
 

packages/projects-docs/pages/sdk/repositories.mdx

@@ -9,7 +9,7 @@ import { Callout } from 'nextra-theme-docs'
 
 By default a Sandbox works like a repository. It has a `.git` folder and it pushes to a remote file system when the Sandbox hibernates.
 
-If you rather want to use an existing remote repository, you can do so by simpy cloning a repository to the sandbox.
+If you rather want to use an existing remote repository, you can do so by simply cloning a repository to the sandbox.
 
 ```ts
 const sandbox = await sdk.sandboxes.create()
@@ -23,7 +23,7 @@ const client = await sandbox.connect({
         // Optionally set credentials
         accessToken: '...',
         provider: 'github.com',
-        username: "foo" // Optional, default tos x-access-token
+        username: "foo" // Optional, defaults to x-access-token
     }
 })
 

packages/projects-docs/pages/sdk/sessions.mdx

@@ -48,7 +48,7 @@ Passing git details allows the user to use git commands inside the sandbox.
 ```ts
 const sandbox = await sdk.sandboxes.create()
 const session = await sandbox.createSession({
-    id: 'some-user-reference,
+    id: 'some-user-reference',
     git: {
         email: 'foo@bar.com', // Required
         name: 'Foo Bar', // Optional, defaults to session id

packages/projects-docs/pages/sdk/templates.mdx

@@ -48,7 +48,7 @@ Now we need to configure the template with tasks so that it will install depende
 The `setupTasks` will run after the Sandbox has started, before any other tasks.
 
 <Callout>
-Do **NOT** start dev servers or other long running porcesses in the `setupTasks`. This will block the setup process and prevent the Sandbox from starting properly.
+Do **NOT** start dev servers or other long running processes in the `setupTasks`. This will block the setup process and prevent the Sandbox from starting properly.
 </Callout>
 
 Now we are ready to deploy the template to our clusters, run: