Fix more spellings

Author: pbiggar

.spelling

@@ -1,6 +1,8 @@
 # Don't add code words here, surround them in code blocks (`) instead
 
 404s
+31-bit
+32-bit
 63-bit
 64-bit
 API
@@ -13,7 +15,6 @@ Asana
 Auth0
 Biggar
 Booleans
-Bucklescript
 CCPA
 CDN
 CLA
@@ -26,7 +27,6 @@ Clojure
 Cloudflare
 Cmd
 CoffeeScript
-Cohttp
 Cron
 Crons
 Ctrl
@@ -48,27 +48,28 @@ HIPAA
 HTTP3
 Haskell
 Honeycomb
-HttpClient
 IFTTT
 ImageMagick
 JS
 JSON
 Javascript
+Kubernetes
 LOC
 MDN
 MacOS
 Mailchimp
-Mono
 Netlify
 Nginx
 NodeJS
+NuGet
 OAuth
 OCaml
 OSX
 Onboarding
 Overwatch
 PHP
 PII
+Paket
 PokeAPI
 Pokemon
 Postgres
@@ -79,6 +80,8 @@ README
 REPL
 REPLs
 RSA
+DSA
+ECDSA
 React
 Read-Eval-Print
 ReasonML
@@ -98,15 +101,19 @@ TestCafe
 Toplevels
 Trello
 Twilio
+UCS-2
 UDP
 UI
 URI
 USERNAME-CANVASNAME
+UTF-16
 UTF-8
-UTF8
 UUID
 UUIDs
+VSCode
 Vue
+WASM
+WebAssembly
 XMLHttpRequest
 ad-hoc
 allowlist
@@ -146,6 +153,7 @@ deserializers
 destructure
 destructuring
 dev
+devcontainer
 dicts
 docstring
 docstrings
@@ -174,6 +182,7 @@ localhost
 macOS
 manager-ish
 meetups
+metadata
 middleware
 minimap
 monorepo
@@ -182,6 +191,7 @@ natively
 omnibox
 param
 params
+pipeable
 pipelining
 popups
 pre-define
@@ -195,7 +205,6 @@ reformats
 renamings
 repo
 repos
-restdb.io
 rollout
 runtime
 serializer
@@ -212,6 +221,7 @@ substrings
 syntaxes
 timelines
 timestamp
+tokenized
 tooltip
 tooltips
 toplevel

README.md

@@ -1,7 +1,7 @@
 # Dark Documentation
 
-Welcome to the source for the [Dark](https://darklang.com) documentation. Contribute
-your improvements as a pull request, or report problems in an issue.
+Welcome to the source for the [Dark](https://darklang.com) documentation.
+Contribute your improvements as a pull request, or report problems in an issue.
 
 View the live docs here: [https://darklang.com/docs](https://darklang.com/docs)
 
@@ -254,14 +254,14 @@ common errors. If you run `npm run format` you should pass the linter.
 
 The `.circleci/config.yml` file describes the CircleCI configuration. It watches
 for commits/merges into the `main` branch, runs a script to generate the
-contents of `gh-pages`, and pushes `gh-pages` to github.
+contents of `gh-pages`, and pushes `gh-pages` to GitHub.
 
 ## Publishing Changes Manually
 
 **NOTE: You shouldn't need to do this because CircleCI runs this
 automatically.**
 
-On the commandline (remember to replace `<YOUR USERNAME>` with your github
+On the commandline (remember to replace `<YOUR USERNAME>` with your GitHub
 username):
 
 ```sh

docs/changelog/release-1.md

@@ -940,10 +940,10 @@ We added a bunch of improved documentation, including:
 
 ![changelog/image2.gif](/img/changelog/image2.gif)
 
-- We asked y'all to not make HttpClient calls to your Dark canvas from REPLs.
+- We asked y'all to not make `HttpClient` calls to your Dark canvas from REPLs.
   We've made some infrastructural changes that fix the issue on our end, so you
   should feel free to do that now. This is useful if you want to create a HTTP
-  trace without leaving Dark. (Note: please don't make HttpClient calls **_to
+  trace without leaving Dark. (Note: please don't make `HttpClient` calls **_to
   Dark_** from HTTP handlers)
 
 ## Week of 1/10/2020

docs/changelog/release-2.md

@@ -132,7 +132,7 @@ users.
   response of status code 418. It now processes the request instead.
 
 - `HttpClient::*` functions called with usernames and passwords in the URL can
-  now support arbitrary UTF8 (in the past, Unicode was not supported.)
+  now support arbitrary UTF-8 (in the past, Unicode was not supported.)
 
 - `X509::pemCertificatePublicKeys` used to only work for RSA keys. It now also
   supports DSA and ECDSA keys. The old version would read ECDSA keys and return
@@ -149,7 +149,7 @@ users.
 
 These breaking changes were documented and announced many months in advance of
 switching over to the new version of Darklang. We also very careful deployed the
-new code, watching for suspiscious changes in any Dark programs that were
+new code, watching for suspicious changes in any Dark programs that were
 running. In the rare case where something went awry, we contacted the users and
 worked with them to ensure a seamless transition.
 
@@ -199,7 +199,7 @@ bare identifiers, while the new version puts them in a string (e.g. `NaN` vs
 This may occur in any of the places in which we generate JSON, which are:
 
 - when responding to a HTTP request in the HTTP framework
-- when making a request with HttpClient (any version)
+- when making a request with `HttpClient` (any version)
 - when calling any of:
   - `Dict::toJson_v0`
   - `Object::toJson_v1` (_deprecated_)
@@ -232,7 +232,7 @@ before).
 Dark parses JSON:
 
 - when receiving a HTTP request in the HTTP framework
-- when receiving a response to a request made with HttpClient (any version)
+- when receiving a response to a request made with `HttpClient` (any version)
 - when calling any of:
 
   - `JSON::parse_v1`
@@ -314,14 +314,14 @@ Behind the scenes, Dark has greatly improved its operations.
 
 - Nodes are now autoscaled, leading to significant cost savings.
 
-- Updated to latest version of kubernetes, cert-manager (which powers our
+- Updated to latest version of Kubernetes, `cert-manager` (which powers our
   [custom domains](https://docs.darklang.com/how-to/custom-domains) feature),
   nginx, and other tools that we use.
 
 - Added internal [feature flagging](https://launchdarkly.com) to give us more
   control over how our infrastructure runs in production
 
-- Significantly increased use of kubernetes' security features, in particular
+- Significantly increased use of Kubernetes' security features, in particular
   internal firewalls.
 
 - Standardized our production deployment process using a tool we wrote called
@@ -338,8 +338,8 @@ Behind the scenes, Dark has greatly improved its operations.
 
 - moved docs to docs.darklang.com
 - [refactored docs](https://github.com/darklang/docs/pull/220) to use the Divio
-  documentation system, categorizing all docs into Tuotials, Reference, How-tos,
-  Walk-throughs and Discussion.
+  documentation system, categorizing all docs into Tutorials, Reference,
+  How-tos, Walk-throughs and Discussion.
 - fixed all links
 - redo the
   [Error Rail discussion](https://docs.darklang.com/discussion/error-handling)
@@ -357,7 +357,7 @@ Behind the scenes, Dark has greatly improved its operations.
   throughout the [darklang repo](https://github.com/darklang/dark)
 
 - Moved 99% of project collaboration to our
-  [public github](https://github.com/darklang/dark) and
+  [public GitHub](https://github.com/darklang/dark) and
   [public community chat](https://darklang.com/discord-invite)
 
 - ported our

docs/changelog/release-3.md

@@ -14,7 +14,7 @@ old features.
   source of annoyance for devs trying to figure out why their code wasn't
   working.
 
-- 64bit ints now work end-to-end (previously we had two separate issues with
+- 64-bit ints now work end-to-end (previously we had two separate issues with
   numbers above `2^53` and numbers above `2^63`)
   ([#4209](https://github.com/darklang/dark/pull/4209))
 

docs/changelog/release-4.md

@@ -34,7 +34,7 @@ August 1, 2022
   ([#4294](https://github.com/darklang/dark/pull/4294)).
 
 - Tuples are not ready ready to release, but much of the behind the scenes work
-  is done, including adding standard library fuctions
+  is done, including adding standard library functions
   ([#4311](https://github.com/darklang/dark/pull/4311)).
 
 - We are working to expose more useful information in the editor, especially

docs/changelog/release-5.md

@@ -74,9 +74,9 @@ Finally, in-progress features can now be enabled for devs, starting with Tuples
   [#4420](https://github.com/darklang/dark/pull/4420),
   [#4426](https://github.com/darklang/dark/pull/4426))
 
-## In-progress features - HttpClient and HTTP framework
+## In-progress features - `HttpClient` and HTTP framework
 
-The current HttpClient and HTTP framework are quite limited, only supporting
+The current `HttpClient` and HTTP framework are quite limited, only supporting
 text request/response bodies, among many other problems. They also lack the
 flexibility to control and compose their behavior.
 

docs/changelog/release-6.md

@@ -131,10 +131,10 @@ _Tuples are in preview - enable them in **Settings/Contributor Settings**_
 - When a handler's route changes, update "open-in-new-window" to use the new
   route ([#4502](https://github.com/darklang/dark/pull/4502))
 
-- dont insert `0` when copy/pasting from the start of ints in patterns
+- don't insert `0` when copy/pasting from the start of ints in patterns
   ([#4492](https://github.com/darklang/dark/pull/4492))
 
-- Dont create empty patterns when creating match
+- Don't create empty patterns when creating match
   ([#4469](https://github.com/darklang/dark/pull/4469))
 
 - put the cursor in right place after a string edit

docs/contributing/adding-your-first-test.md

@@ -7,7 +7,7 @@ for a built-in function. This will get you through the process of contributing
 and get you familiar with how to get code into Dark.
 
 _We're assuming you've got the repo is set up and the `builder` script is
-running (or if you're running the devcontainer in VSCode, that the decvontainer
+running (or if you're running the devcontainer in VSCode, that the devcontainer
 is running)!_
 
 ## Adding the test

docs/contributing/repo-layout.md

@@ -10,8 +10,8 @@ here's how the various directories intersect, and what language they use:
 ## Directory listing
 
 - `.circleci` - CI config file
-- `.ionide` - config for F# VsCode plugin
-- `.vscode` - VsCode config
+- `.ionide` - config for F# VSCode plugin
+- `.vscode` - VSCode config
 - `auth0-branding` - has some assets for our login provider
 - `client` - the editor, and the entire frontend application that is found under
   [darklang.com/a/yourcanvas](http://darklang.com/a/yourcanvas) (note, not
@@ -50,13 +50,13 @@ here's how the various directories intersect, and what language they use:
 - `backend` - The backend written in F# and .NET. including the language
   definition and execution engine, the "framework" (HTTP, DB, queues, etc), the
   editor's HTTP API, and the execution engine which runs in the client.
-  - `.paket` - Used by the paket/nuget package manager
+  - `.paket` - Used by the Paket/NuGet package manager
   - `Build` - where the compiler puts compiled code
-  - `paket-files` - Used by the paket/nuget package manager
+  - `paket-files` - Used by the Paket/NuGet package manager
   - `src/ApiServer` - webserver serving the editor and the API used by the
     editor
-  - `src/BackendOnlyStdLib` - impl. of functions which need to be run on the
-    backend, due to their connection to the DB, queues, etc.
+  - `src/BackendOnlyStdLib` - implementation of functions which need to be run
+    on the backend, due to their connection to the DB, queues, etc.
   - `src/Benchmark` - a benchmark executable to measure the performance of Dark
     code
   - `src/BwdServer` - webserver that is grand-user facing (at builtwithdark.com)

docs/contributing/rescript-and-fsharp-for-dark-developers.md

@@ -124,7 +124,7 @@ libraries from `.NET`, FSharp.Core, or if necessary, the FSharpPlus library.
 ### Int
 
 An `int` is the same in Dark and F#, same syntax, same meaning. Note that ints
-are 31 bits in ReScript, 32 bits in F#, and 64bit in Dark.
+are 31-bit in ReScript, 32-bit in F#, and 64-bit in Dark.
 
 ```fsharp
 let x = 5
@@ -442,7 +442,7 @@ type t =
 
 Type `t` (it's a common convention to name the main type of a module `t`) must
 be one of `EInteger`, `EBool`, `EString`, etc. `EInteger` takes two parameters,
-an `id` and a `string` (we use a string to represent integers as Bucklescript
+an `id` and a `string` (we use a string to represent integers as ReScript
 doesn't have a big enough integer type).
 
 To create a `t`, you'd do something like this:
@@ -477,7 +477,7 @@ list->List.map((elem) => elem + 2)
 
 It's very common to use functions like `List.map` which have a parameter called
 `f` which take a lambda. In F#, above, that parameter is passed like any other.
-In ReScript, those parameters are passed as labelled variables:
+In ReScript, those parameters are passed as labeled variables:
 
 ```rescript
 list->List.map:(~f=((elem) => elem + 2))
@@ -563,7 +563,7 @@ print(myString)
 For functions that perform IO, you'll need to use the `ply` or `task`
 "computation expression". A "computation expression" is a special F# language
 feature for writing abstractions with a nice syntax. The `ply` CE allows using a
-specialized asyncronous structure called Ply (which is extremely similar to a
+specialized asynchronous structure called Ply (which is extremely similar to a
 .Net Task) easily, and can best be illustrated with an example:
 
 ```fsharp
@@ -589,10 +589,10 @@ Let's break this down line by line:
   `Ply`, in this case a `Ply<Dval>`.
 
 Why do we go through all this trouble? Because this is an async runtime, and
-`let!` and `return` are the enablers of the asyncronicity. A `Ply` is a promise,
-and `let!` waits for the promise and then continues (running other code while
-the IO is still pending). This is the exact same as the `async` keyword in JS,
-Rust, C# or Python.
+`let!` and `return` are the enablers of the asynchronicity. A `Ply` is a
+promise, and `let!` waits for the promise and then continues (running other code
+while the IO is still pending). This is the exact same as the `async` keyword in
+JS, Rust, C# or Python.
 
 Note that while we primarily use `Ply` and `uply` inside the Interpreter, most
 of our other async code use `Task` and `task`. These are interchangeable except

docs/contributing/tour-of-editor.md

@@ -6,7 +6,7 @@ The editor is in `client/`. We refer to it as the client or the editor (we don't
 call it the frontend though).
 
 It started life as an Elm application, and still uses the Elm Architecture
-(which we like). The current app is in Bucklescript.
+(which we like). The current app is in ReScript.
 
 ## Elm architecture
 

docs/contributing/troubleshooting.md

@@ -13,7 +13,7 @@ If you're having problems contributing, we want to help:
 Common fixes:
 
 - Sometimes there are compilation problems where the build caches from various
-  package managers we use (npm, nuget) develop problems. They can be fixed by
+  package managers we use (NPM, NuGet) develop problems. They can be fixed by
   clearing the build directories (which are in Docker volumes) by running the
   related scripts:
   - for client errors, use `./scripts/clear-bs-cache` and