Fix some typos

3 files changed, 7 insertions, 7 deletions

diff --git a/api-conventions.md b/api-conventions.md
index 44e78b1..eb5e6be 100644
--- a/api-conventions.md
+++ b/api-conventions.md
@@ -50,7 +50,7 @@ A singleton which is owned by `:resource`.
 
 OR
 
-A named action to be completed asyncronously.
+A named action to be completed asynchronously.
 
 ### /api/:resource/:id/:subresource/:id
 
@@ -117,7 +117,7 @@ Errors are returned with a consistent response body:
     "errors": [
       {
         "field": "example",
-        "reason": "example is requried"
+        "reason": "example is required"
       }
     ]
   }
@@ -199,7 +199,7 @@ that occurred, e.g. `profile:update`.
 The `X-Payload-Signature` and `X-Payload-Nonce` headers can be used to verify
 the authenticity of the webhook payload. Concatenate the request body with the
 nonce (treat the nonce as an ASCII-encoded string) and use it to verify the
-base64-encoded Ed25519 siganture given by the `X-Payload-Signature` header. The
+base64-encoded Ed25519 signature given by the `X-Payload-Signature` header. The
 public key (also base64 encoded) is
 `uX7KWyyDNMaBma4aVbJ/cbUQpdjqczuCyK/HxzV/u+4=`. Here's an example of verifying
 the payload in Python:
diff --git a/tutorials/builds.sr.ht/using-build-secrets.md b/tutorials/builds.sr.ht/using-build-secrets.md
index bcd965e..4a6e5dd 100644
--- a/tutorials/builds.sr.ht/using-build-secrets.md
+++ b/tutorials/builds.sr.ht/using-build-secrets.md
@@ -10,7 +10,7 @@ available to CI jobs.
 ## Our example build manifest
 
 Let's say we have a git repo with static HTML files that we'd like to deploy by
-sending them to our webserver. A simple build manifest might look like this:
+sending them to our web server. A simple build manifest might look like this:
 
 ```yml
 image: alpine/edge
@@ -54,10 +54,10 @@ next step.
 
 Go to the [builds.sr.ht secret management
 dashboard](https://builds.sr.ht/secrets) and select "SSH key" for secret type,
-then paste your key into the textbox. Click "submit" - and your new secret
+then paste your key into the text box. Click "submit" - and your new secret
 should show up on the right, along with its UUID.
 
-This UUID is used to uniquely identify this secret in build manifets. Copy this
+This UUID is used to uniquely identify this secret in build manifests. Copy this
 UUID for the next step.
 
 ## Adding secrets to your build manifest
diff --git a/tutorials/getting-started-with-builds.md b/tutorials/getting-started-with-builds.md
index f902f01..b1440d2 100644
--- a/tutorials/getting-started-with-builds.md
+++ b/tutorials/getting-started-with-builds.md
@@ -3,7 +3,7 @@ title: Getting started with builds.sr.ht
 ---
 
 builds.sr.ht is our build automation platform. We're going to walk through the
-process of running jobs on builds.sr.ht and a look at few useful features.
+process of running jobs on builds.sr.ht and a look at a few useful features.
 
 ## Build manifests