Spelling suggestions (#146)

* Spelling suggestions

* Apply suggestions from code review

Co-authored-by: Jeremy Walker <[email protected]>

Author: axtens

building/markdown/markdown.md

@@ -11,7 +11,7 @@ All rules are being added to our CI and linting tools, and should be adhered to
 - All files must start start with a level-1 heading (`# Some heading text`).
 - Level-1 headings exist purely for consuming on GitHub or equivalent.
 - If the file is rendered by Exercism (e.g. displayed on the website, rendered via the CLI), this heading will be removed, and a contextual heading will be inserted.
-- No heading may decend a level greater than one below the previous (e.g. `##` may only be followed by `###`, not `####`).
+- No heading may descend a level greater than one below the previous (e.g. `##` may only be followed by `###`, not `####`).
 - Beyond the single level-1 (`#`) heading, only level-2 (`##`), level-3 (`###`) and level-4 (`####`) headings may be used.
 
 ## Links

building/tooling/README.md

@@ -7,7 +7,7 @@ Tooling is (generally) written in the language of the specific track, and is bui
 
 All tooling is deployed using the same Docker workflow.
 
-There are currently three pices of tooling:
+There are currently three pieces of tooling:
 
 - **[Test Runners](./test-runners)**
 - **[Representers](./representers)**

building/tooling/analyzers/interface.md

@@ -73,7 +73,7 @@ The following `type`s are valid:
 Comments without a type field default to `informative `.
 
 Currently in the website, we soft-block on essential comments, encourage students to complete actionable comments before marking as complete on Practice Exercises (but not Concept Exercises), but don't suggest any action on `informative` or `celebratory`.
-However, in the future we may choose to add emojis or indicators to other types, or group them seperately.
+However, in the future we may choose to add emojis or indicators to other types, or group them separately.
 
 ## Debugging
 
@@ -139,9 +139,9 @@ In this document, **de facto** is defined as follows:
   position by public acceptance or market forces. Unofficial customs that are
   widely accepted.
 
-In other words, if a nearly all developers (non-hobyists) who write code in a
+In other words, if a nearly all developers (non-hobbyists) who write code in a
 certain language have established certain rules, these rules are a **de facto
-standard** and become idiomatic use. Example: **Ruby** uses 2 space identation.
+standard** and become idiomatic use. Example: **Ruby** uses 2 space indentation.
 
 Some rules are language features, even if they are not documented well. These
 language features are part of "idiomatic rules" and not stylistic choices.
@@ -197,7 +197,7 @@ to the official rules.
 > - :speech*balloon: if it's a \_stylistic* preference, **and** there is _one
 >   clear standard_, comment on it. These rules enforce idiomatic code.
 > - :question: If it's a _stylistic_ preference, **and** there is no clear
->   standard, but most to all non-hobyist have adopted the same style, this
+>   standard, but most to all non-hobbyist have adopted the same style, this
 >   might be idiomatic. Comment at your discretion.
 
 #### Examples

building/tooling/docker.md

@@ -7,7 +7,7 @@ It should live at the root directory of your repository and should be called `Do
 
 The Dockerfile should create the minimal image needed for the tooling to function correctly and speedily.
 
-The Dockerfile should produce an image with as a small a size as possible while maximising (and prioritising) perfomance.
+The Dockerfile should produce an image with as a small a size as possible while maximising (and prioritising) performance.
 Applying the official [Dockerfile best practices](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/) can help to create a minimal image.
 
 ## Execution
@@ -53,7 +53,7 @@ To use the internal network, first run `docker network create --internal interna
 
 ### Memory
 
-Languages can set the maximum memory they need to use to run their jobs. Setting this to be as low as possible means that we can run more jobs more quickly in parallel. It also means that people who try and abuse memory will not be able to succeed. Different langauges need wildly different maximum memory usage. Benchmarking the execution of a docker run to establish the maximum memory it uses is advised and appreciated.
+Languages can set the maximum memory they need to use to run their jobs. Setting this to be as low as possible means that we can run more jobs more quickly in parallel. It also means that people who try and abuse memory will not be able to succeed. Different languages need wildly different maximum memory usage. Benchmarking the execution of a docker run to establish the maximum memory it uses is advised and appreciated.
 
 Memory [should be specified](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory) using the number with suffix of b, k, m, g, to indicate bytes, kilobytes, megabytes, or gigabytes.
 

building/tooling/representers/README.md

@@ -25,7 +25,7 @@ A notification will be sent for old solutions with a matching representation.
 Each language has it's own representer, written in that language.
 The website acts as the orchestrator between the representer and students' submissions.
 
-Each representer lives in the Exercism GitHub organsation in a repository named `$LANG-representer` (e.g. `ruby-representer`).
+Each representer lives in the Exercism GitHub organisation in a repository named `$LANG-representer` (e.g. `ruby-representer`).
 You can explore the different representers [here](https://github.com/exercism?q=-representer).
 
 If you would like to get involved in helping with an existing Representer, please open an issue in its repository asking if there is somewhere you can help.

building/tooling/test-runners/interface.md

@@ -138,7 +138,7 @@ The per-test `output` key should be used to store and output anything that a use
 - It should be attached to all test results that produce user output.
 - Only content outputted by a user manually should show - not automatic output by the test-runner.
 - You may either capture content that is output through normal means (e.g. `puts` in Ruby, `print` in Python or `Debug.WriteLine` in C#), or you may provide a method that the user may use (e.g. the Ruby Test Runner provides a user with a globally available `debug` method that they can use, which has the same characteristics as the standard `puts` method).
-- The output **must** be limited to 500 chars. Either truncating with a message of "Output was truncated. Please limit to 500 chars" or returning an error in this situation are acceptible.
+- The output **must** be limited to 500 chars. Either truncating with a message of "Output was truncated. Please limit to 500 chars" or returning an error in this situation are acceptable.
 
 ### UI/UX concerns
 
@@ -168,6 +168,6 @@ Test Code:
 All roads lead to Rome and there is no prescribed pattern to arrive at this.
 There are several approaches taken so far:
 
-- Auxillary JSON files compiled manually, merged with test results during the test run-time.
+- Auxiliary JSON files compiled manually, merged with test results during the test run-time.
 - Automated static analysis of the test suite, merged with test results during the test run-time.
   - This may be accomplished by AST analysis or text-parsing

building/tracks/ci/workflow-templates.md

@@ -52,7 +52,7 @@ It can be very helpful to make the actions that should run, available locally as
 
 > "But the command is very short, e.g. `eslint . --ext ts --ext tsx`".
 >
-> When this command needs to be updated, it now needs to update in all the places in the documentation, the workflow files, ánd in the _minds of the maintainers_. Extracting this to a script resolves all that. Reading a workflow file can also be **very** daunting.
+> When this command needs to be updated, it now needs to update in all the places in the documentation, the workflow files, and in the _minds of the maintainers_. Extracting this to a script resolves all that. Reading a workflow file can also be **very** daunting.
 
 ### Checks on PRs where exercises change
 

building/tracks/concept-exercises.md

@@ -126,7 +126,7 @@ my_first_variable = SomeComplexObject.new
 
 The `introduction.md` document introduces the exercise's concept(s) to the student. Each concept also has its _own_ [`introduction.md` document](./concepts#fileintroductionmd), which is not shown outside the context of an exercise.
 
-If the concept's introduction should be included verbatim in the exercise's introduction, an `introduction.md.tpl` file can be used. This file allows refering to concept introductions through placeholders: `%{concept:<concept-slug>}`.
+If the concept's introduction should be included verbatim in the exercise's introduction, an `introduction.md.tpl` file can be used. This file allows referring to concept introductions through placeholders: `%{concept:<concept-slug>}`.
 
 [configlet](./configlet/generating.md) can generate an `introduction.md` file from a template file. The generated file will have the concept placeholders replaced by the concept's `introduction.md` contents.
 
@@ -166,7 +166,7 @@ We place high value on making Exercism's content safe for everyone and so often
 
 - Try to make sure the story is welcoming and can be understood by everyone. If the story contains in-jokes or regional slang, try to think of alternative phrases.
 - Try to write examples that are inclusive to everyone. For example, consider using names from other cultures and mixed genders.
-- Ask yourself whether you know anyone personally who would take offense by the story. If that's the case, consider changing it to avoid it.
+- Ask yourself whether you know anyone personally who would take offence by the story. If that's the case, consider changing it to avoid it.
 
 #### Example
 
@@ -476,7 +476,7 @@ Each exercise also has a _slug_, which is normalized version of the exercise nam
 
 1. Use lowercase.
 1. Use [kebab-case][kebab-case].
-1. Use latin alphanumerical characters and dashes (Regexp: `[a-z0-9-]+`)
+1. Use Latin alphanumerical characters and dashes (Regexp: `[a-z0-9-]+`)
 1. Prefer written digits over numeric ones, unless there is a specific reason to prefer the digit (e.g. `two-fer` over `2-fer`)
 
 Good examples of slugs:

building/tracks/concepts.md

@@ -75,7 +75,7 @@ Here some examples of what could be covered.
 - Performance characteristics and memory usage, when a common consideration within that language
 - Don't refer to an exercise in the text, as this file is displayed outside the context of an exercise.
 
-It is **not** the aim of the `about.md` file to provide a complete set of information on the Concept. As an example, imagine a language that has some older features for which experienced programmers (and maybe even the official docs/specs) recommend they should not be used anymore. Providing details on such features would be out of scope for the `about.md` file because they are not relevant to gain fluency. However, maintainers may choose to add a short block to acknowledge the old standards if a student might commonly come across those standards in the wild. However, this block should be demarked as such.
+It is **not** the aim of the `about.md` file to provide a complete set of information on the Concept. As an example, imagine a language that has some older features for which experienced programmers (and maybe even the official docs/specs) recommend they should not be used anymore. Providing details on such features would be out of scope for the `about.md` file because they are not relevant to gain fluency. However, maintainers may choose to add a short block to acknowledge the old standards if a student might commonly come across those standards in the wild. However, this block should be marked as such.
 
 The `about.md` file MUST be clearly structured, especially when it contains a lot of information. In the future there will also be support for marking parts as "advanced topics" to point them out to interested students without overloading others.
 

building/tracks/practice-exercises.md

@@ -1,6 +1,6 @@
 # Practice Exercises
 
-[Practice Exercises](../../product/practice-exercises.md) are exercises designed to allow students to solve an arbitary problem, with the aim of them making use of the concepts they have learnt so far.
+[Practice Exercises](../../product/practice-exercises.md) are exercises designed to allow students to solve an arbitrary problem, with the aim of them making use of the concepts they have learnt so far.
 
 ## Metadata
 
@@ -108,7 +108,7 @@ We place high value on making Exercism's content safe for everyone and so often
 
 - Try to make sure the story is welcoming and can be understood by everyone. If the story contains in-jokes or regional slang, try to think of alternative phrases.
 - Try to write examples that are inclusive to everyone. For example, consider using names from other cultures and mixed genders.
-- Ask yourself whether you know anyone personally who would take offense by the story. If that's the case, consider changing it to avoid it.
+- Ask yourself whether you know anyone personally who would take offence by the story. If that's the case, consider changing it to avoid it.
 
 #### Example
 
@@ -150,7 +150,7 @@ We place high value on making Exercism's content safe for everyone and so often
 
 - Try to make sure the story is welcoming and can be understood by everyone. If the story contains in-jokes or regional slang, try to think of alternative phrases.
 - Try to write examples that are inclusive to everyone. For example, consider using names from other cultures and mixed genders.
-- Ask yourself whether you know anyone personally who would take offense by the story. If that's the case, consider changing it to avoid it.
+- Ask yourself whether you know anyone personally who would take offence by the story. If that's the case, consider changing it to avoid it.
 
 #### Example