Fix typos

deploy/api/index.md

@@ -68,7 +68,7 @@ Deploy.
 - [`Deno.resolveDns`](https://docs.deno.com/api/deno/~/Deno.resolveDns) - Make
  DNS queries
 - File system API
- - [`Deno.cwd`](hhttps://docs.deno.com/api/deno/~/Deno.cwd) - Get the current
+ - [`Deno.cwd`](https://docs.deno.com/api/deno/~/Deno.cwd) - Get the current
  working directory
  - [`Deno.readDir`](https://docs.deno.com/api/deno/~/Deno.readDir) - Get
  directory listings

deploy/kv/manual/backup.md

@@ -128,7 +128,7 @@ and the region the bucket is in. Then click "Save".
 />
 
 The backup will start immediately. Once the data has been backed up, and
-continous backup is active, you will see the status change to "Active".
+continuous backup is active, you will see the status change to "Active".
 
 ## Configuring backup to Google Cloud Storage
 
@@ -215,7 +215,7 @@ Cloud Storage". Enter the bucket name, access key ID, and secret access key you
 created earlier, and the region the bucket is in. Then click "Save".
 
 The backup will start immediately. Once the data has been backed up, and
-continous backup is active, you will see the status change to "Active".
+continuous backup is active, you will see the status change to "Active".
 
 ## Using backups
 

deploy/kv/manual/index.md

@@ -245,7 +245,7 @@ by your code. Learn more about Deno KV on Deno Deploy [here](./on_deploy).
 
 By default, [`Deno.openKv()`](https://docs.deno.com/api/deno/~/Deno.openKv)
 creates or opens a persistent store based on the path from which the script that
-invoked it was run. This isn't usually desireable for tests, which need to
+invoked it was run. This isn't usually desirable for tests, which need to
 produce the same behavior when run many times in a row.
 
 To test code that uses Deno KV, you can use the special argument `":memory:"` to

deploy/kv/manual/queue_overview.md

@@ -171,10 +171,10 @@ once per message. See
 handler is invoked to process your queued messages when they're ready for
 delivery. If your handler throws an exception the runtime will automatically
 retry to call the handler again until it succeeds or until maximum retry
-attempts are reached. The message is considered to be succesfully processed once
-the
+attempts are reached. The message is considered to be successfully processed
+once the
 [`listenQueue`](https://docs.deno.com/api/deno/~/Deno.Kv.prototype.listenQueue)
-handler invocation completes succesfully. The message will be dropped if the
+handler invocation completes successfully. The message will be dropped if the
 handler consistently fails on retries.
 
 ### Message delivery order

deploy/manual/deployctl.md

@@ -16,7 +16,7 @@ running the following command:
 curl -fsSL https://deno.land/install.sh | sh
 ```
 
-You don't need to setup a Deno Deploy account beforhand. It will be created
+You don't need to setup a Deno Deploy account beforehand. It will be created
 along the way when you deploy your first project.
 
 ## Install `deployctl`

runtime/manual/getting_started/setup_your_environment.md

@@ -254,7 +254,7 @@ support Deno.
 
 ### Kakoune
 
-[Kakoune](http://kakoune.org/) supports connecting to the Deno language server
+[Kakoune](https://kakoune.org/) supports connecting to the Deno language server
 via the [kak-lsp](https://github.com/kak-lsp/kak-lsp) client. Once
 [kak-lsp is installed](https://github.com/kak-lsp/kak-lsp#installation) an
 example of configuring it up to connect to the Deno language server is by adding

runtime/manual/node/index.md

@@ -17,7 +17,7 @@ more about these methods.
 
 ## Unstable compatibility features
 
-Node and npm compatiblity is an ongoing project for the Deno team. As such,
+Node and npm compatibility is an ongoing project for the Deno team. As such,
 there are a number of unstable features aimed at improving compatibility that
 you may want to reference. Please check out the
 [unstable feature flags](/runtime/manual/tools/unstable_flags) documentation for

runtime/manual/references/contributing/profiling.md

@@ -547,7 +547,7 @@ Options:
  type: size_t default: 0
  --initial-heap-size (initial size of the heap (in Mbytes))
  type: size_t default: 0
- --huge-max-old-generation-size (Increase max size of the old space to 4 GB for x64 systems withthe physical memory bigger than 16 GB)
+ --huge-max-old-generation-size (Increase max size of the old space to 4 GB for x64 systems with the physical memory bigger than 16 GB)
  type: bool default: true
  --initial-old-space-size (initial old space size (in Mbytes))
  type: size_t default: 0

subhosting/manual/quick_start.md

@@ -172,7 +172,7 @@ like this:
 }
 ```
 
-Note the `id` of the project that was returned with this repsonse - this is the
+Note the `id` of the project that was returned with this response - this is the
 project ID we'll use in the next step.
 
 Now that we have REST API access configured and a project set up, we can move on