Fix typos in the documentation. (#731)

Co-authored-by: mundry <mundry@users.noreply.github.com>

2 files changed, 2 insertions, 2 deletions

diff --git a/docs/src/pages/reference/api-reference.md b/docs/src/pages/reference/api-reference.md
index 1be5d3c2c..9667af2ec 100644
--- a/docs/src/pages/reference/api-reference.md
+++ b/docs/src/pages/reference/api-reference.md
@@ -173,7 +173,7 @@ Astro will generate an RSS 2.0 feed at `/feed/[collection].xml` (for example, `/
 
 All ESM modules include a `import.meta` property. Astro adds `import[dot]meta[dot]env` through [Snowpack](https://www.snowpack.dev/).
 
-**`import[dot]meta[dot]env[dot]SSR`** can be used to know when rendering on the server. Some times you might want different logic, for example a component that should only be rendered in the client:
+**`import[dot]meta[dot]env[dot]SSR`** can be used to know when rendering on the server. Sometimes you might want different logic, for example a component that should only be rendered in the client:
 
 ```jsx
 import { h } from 'preact';
diff --git a/docs/src/pages/reference/renderer-reference.md b/docs/src/pages/reference/renderer-reference.md
index 568650fe7..542905efe 100644
--- a/docs/src/pages/reference/renderer-reference.md
+++ b/docs/src/pages/reference/renderer-reference.md
@@ -9,7 +9,7 @@ Internally, each framework is supported via a framework **renderer.** A renderer
 
 ## What is a renderer?
 
-A renderer is an NPM package that has two responsiblities:
+A renderer is an NPM package that has two responsibilities:
 
 1. _render a component to a static string of HTML_ at build time
 2. _rehydrate that HTML to create an interactive component_ on the client.