summaryrefslogtreecommitdiff
path: root/docs/getting_started/typescript.md
diff options
context:
space:
mode:
authorKhang Dinh <thesephi@gmail.com>2020-05-21 18:40:02 +0200
committerGitHub <noreply@github.com>2020-05-21 12:40:02 -0400
commit65f4e5912293bea5c59e2923cabfa8c0373a05a7 (patch)
tree2711a11d0779dd6962dcfda48ace44f5f7941b9f /docs/getting_started/typescript.md
parent49c85a2c2396d6d010296503faf0b0b8712e9cd0 (diff)
typos (#5713)
Diffstat (limited to 'docs/getting_started/typescript.md')
-rw-r--r--docs/getting_started/typescript.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/getting_started/typescript.md b/docs/getting_started/typescript.md
index 35a513b37..197c41482 100644
--- a/docs/getting_started/typescript.md
+++ b/docs/getting_started/typescript.md
@@ -24,7 +24,7 @@ takes the form of a compiler hint. Compiler hints inform Deno the location of
`.d.ts` files and the JavaScript code that is imported that they relate to. The
hint is `@deno-types` and when specified the value will be used in the compiler
instead of the JavaScript module. For example, if you had `foo.js`, but you know
-that along side of it was `foo.d.ts` which was the types for the file, the code
+that alongside of it was `foo.d.ts` which was the types for the file, the code
would look like this:
```ts
@@ -48,7 +48,7 @@ If you are hosting modules which you want to be consumed by Deno, and you want
to inform Deno about the location of the type definitions, you can utilize a
triple-slash directive in the actual code. For example, if you have a JavaScript
module and you would like to provide Deno with the location of the type
-definitions which happen to be alongside that file, your JavaScript module named
+definition which happens to be alongside that file, your JavaScript module named
`foo.js` might look like this:
```js