Patch for wiki page spelling

[JeremyLWright]

From 232fc0f31b81f123e880f8cb56f2ac4a6912d8c1 Mon Sep 17 00:00:00 2001
From: Jeremy Wright <jeremy.wright@joylabs.com>
Date: Wed, 17 Mar 2021 10:11:08 -0700
Subject: [PATCH] Fix a few misspellings.

---
 Getting-Started.md        | 4 ++--
 Setting-up-Environment.md | 2 +-
 Settings.md               | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Getting-Started.md b/Getting-Started.md
index b8dbfec..d3e7d72 100644
--- a/Getting-Started.md
+++ b/Getting-Started.md
@@ -38,8 +38,8 @@ Run command `TLA+: Parse module`. It will translate the PlusCal algorithm to a T

 We now have a simple specification that we can check by running the command `TLA+: Check model`. It will start the TLC tool on the currently open specification and display its progress and final result in a special panel.

-One of the artefacts that the TLC command cerates when running on a `.tla` file with a PlusCal algorithm is a `.cfg` file that contains the model parameters. If you don't use PlusCal in your specification, the model configuration file will not be created automatically, but the extension will warn you about its absence and propose you to create it from a simple template.
+One of the artifacts that the TLC command creates when running on a `.tla` file with a PlusCal algorithm is a `.cfg` file that contains the model parameters. If you don't use PlusCal in your specification, the model configuration file will not be created automatically, but the extension will warn you about its absence and propose you to create it from a simple template.

 You can find the full output of the TLC tool in a `.out` file that will be created near your specification. Should you need to visualize an output from a previous model checking, use the command `TLA+: Visualize TLC output` on a `.out` file.

-Should you have any problems while checking the TLA<sup>+</sup> module or running TLC, please, refer to the [Troubleshooting](/alygin/vscode-tlaplus/wiki/Troubleshooting) page, it might provide a solution.
\ No newline at end of file
+Should you have any problems while checking the TLA<sup>+</sup> module or running TLC, please, refer to the [Troubleshooting](/alygin/vscode-tlaplus/wiki/Troubleshooting) page, it might provide a solution.
diff --git a/Setting-up-Environment.md b/Setting-up-Environment.md
index e3535ee..a3867b7 100644
--- a/Setting-up-Environment.md
+++ b/Setting-up-Environment.md
@@ -4,5 +4,5 @@ If you have already [installed](/alygin/vscode-tlaplus/wiki/How-to-Install) the
 - Configure [automatic module parsing](/alygin/vscode-tlaplus/wiki/Automatic-Module-Parsing)
 - Adjust [formatting options](/alygin/vscode-tlaplus/wiki/Formatting-Preferences) to your liking
 - Improve [visualization of your specifications](/alygin/vscode-tlaplus/wiki/Fonts)
-- Install the [vscode-pdf](https://marketplace.visualstudio.com/items?itemName=tomoki1207.pdf) extension to preview specificaion PDFs
+- Install the [vscode-pdf](https://marketplace.visualstudio.com/items?itemName=tomoki1207.pdf) extension to preview specification PDFs
 - Learn how to [visualize generated states](/alygin/vscode-tlaplus/wiki/Visualizing-States)
diff --git a/Settings.md b/Settings.md
index 08da067..490d75a 100644
--- a/Settings.md
+++ b/Settings.md
@@ -14,7 +14,7 @@ These settings are available in the Extensions &rarr; TLA+ section of the [Setti

 ## Other Useful Settings

-These settings and configuration tricks are not provided by the extension itself, but leverage the general VS Code platform capabilibies:
+These settings and configuration tricks are not provided by the extension itself, but leverage the general VS Code platform capabilities:

 * [Keyboard Shortcuts](/alygin/vscode-tlaplus/wiki/Keyboard-Shortcuts)
 * [Automatic Module Parsing](/alygin/vscode-tlaplus/wiki/Automatic-Module-Parsing)
--
2.24.3 (Apple Git-128)

[JeremyLWright]

Thank you for the wonderful Extension!

[alygin]

@JeremyLWright, thanks for the patch! Applied.