summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/contributing/release_schedule.md2
-rw-r--r--docs/contributing/style_guide.md4
-rw-r--r--docs/examples/import_export.md4
-rw-r--r--docs/runtime/workers.md2
-rw-r--r--docs/tools/linter.md2
5 files changed, 7 insertions, 7 deletions
diff --git a/docs/contributing/release_schedule.md b/docs/contributing/release_schedule.md
index e48bc2ae9..8aabac9c8 100644
--- a/docs/contributing/release_schedule.md
+++ b/docs/contributing/release_schedule.md
@@ -22,7 +22,7 @@ canary release by running:
deno upgrade --canary
```
-To update to a specifc canary, pass the commit has in the `--version` option:
+To update to a specific canary, pass the commit has in the `--version` option:
```
deno upgrade --canary --version=973af61d8bb03c1709f61e456581d58386ed4952
diff --git a/docs/contributing/style_guide.md b/docs/contributing/style_guide.md
index 3f190ecf3..d834ea91a 100644
--- a/docs/contributing/style_guide.md
+++ b/docs/contributing/style_guide.md
@@ -283,7 +283,7 @@ comment. If it needs further comments it is not a good example.
Currently, the building process uses `dlint` to validate linting problems in the
code. If the task requires code that is non-conformant to linter use
-`deno-lint-ignore <code>` directive to supress the warning.
+`deno-lint-ignore <code>` directive to suppress the warning.
```typescript
// deno-lint-ignore no-explicit-any
@@ -349,7 +349,7 @@ export function foo(): string {
programs can rely on. We want to guarantee to users that this code does not
include potentially unreviewed third party code.
-#### Document and maintain browser compatiblity.
+#### Document and maintain browser compatibility.
If a module is browser compatible, include the following in the JSDoc at the top
of the module:
diff --git a/docs/examples/import_export.md b/docs/examples/import_export.md
index e87980bc7..1fa194d0c 100644
--- a/docs/examples/import_export.md
+++ b/docs/examples/import_export.md
@@ -63,7 +63,7 @@ from a locally stored arithmetic module. The same functionality can be created
by importing `add` and `multiply` methods from a remote module too.
In this case the Ramda module is referenced, including the version number. Also
-note a JavaScript module is imported directly into a TypeSript module, Deno has
+note a JavaScript module is imported directly into a TypeScript module, Deno has
no problem handling this.
**Command:** `deno run ./remote.ts`
@@ -115,6 +115,6 @@ export function multiply(a: number, b: number): number {
```
All functions, classes, constants and variables which need to be accessible
-inside external modules must be exported. Either by prepending them with the
+inside external modules must be exported. Either by pretending them with the
`export` keyword or including them in an export statement at the bottom of the
file.
diff --git a/docs/runtime/workers.md b/docs/runtime/workers.md
index 019df7201..5dcf05915 100644
--- a/docs/runtime/workers.md
+++ b/docs/runtime/workers.md
@@ -11,7 +11,7 @@ the `type: "module"` option when creating a new worker.
Relative module specifiers are
[not supported](https://github.com/denoland/deno/issues/5216) at the moment. You
-can instead use the `URL` contructor and `import.meta.url` to easily create a
+can instead use the `URL` constructor and `import.meta.url` to easily create a
specifier for some nearby script.
```ts
diff --git a/docs/tools/linter.md b/docs/tools/linter.md
index 709e0d644..4e432034b 100644
--- a/docs/tools/linter.md
+++ b/docs/tools/linter.md
@@ -106,7 +106,7 @@ function foo(): any {
}
```
-Ignore directive must be placed before first stament or declaration:
+Ignore directive must be placed before first statement or declaration:
```ts
// Copyright 2020 the Deno authors. All rights reserved. MIT license.