Update typos and document clarifications

Author: Dan Humphrey

docs/api/plugins/introduction.md

@@ -14,7 +14,7 @@ The API is structured per domain of power (e.g. playback, record etc...).
 
 ### Versioning
 
-`uri`s in the api start at `/`, and are versioned, the current living version is 1, calling a `uri` with no version means the latest one.  
+`uri`s in the API start at `/`, and are versioned, the current living version is 1, calling a `uri` with no version means the latest one.  
 
 - `/register` - latest version of the register function.
 - `/v1/register` - register `v1`
@@ -32,23 +32,23 @@ Each one determines different functionality on the resource.
 
 ### Errors
 
-When sending a request Selenium IDE will either not respond (if the window is closed), in which case the Promise will reject.  
+If the window is closed when a request is sent, Selenium IDE will not respond and the Promise will reject.  
 
-Or if Selenium IDE is open it can either succeed which will resolve the Promise, or pass a "userland" error back to you, since errors can't be serialized.  
+Alternatively, if Selenium IDE is open it can either succeed which will resolve the Promise, or pass a "userland" error back to you, since errors can't be serialized.  
 
-#### Connection Error
+#### Connection error
 
-Connection error will happen when the IDE window is closed, therefore the promise will reject.
+A Connection error will occur when the IDE window is closed, therefore the promise will reject.
 
 ```js
 browser.runtime.sendMessage(SIDE_ID, payload).catch((error) => {
   console.error(error); // connection error
 });
 ```
 
-#### Request Error
+#### Request error
 
-Request error will happen when a request is invalid, for example request a resource that doesn't exist, like [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API), such requests **resolve** the promise with errors attached on them.
+A Request error will occur when a request is invalid, for example a request for a resource which doesn't exist, like [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API). Such requests **resolve** the promise with errors attached on them.
 
 ```js
 browser.runtime.sendMessage(SIDE_ID, payload).then((response) => {
@@ -60,7 +60,7 @@ browser.runtime.sendMessage(SIDE_ID, payload).then((response) => {
 
 #### Successful Request
 
-A successful request is one where `error` is not defined on the response object, each endpoint has its own response, most `post` will respond with `true` if succeeded.
+A successful request is one where `error` is not defined on the response object. Each endpoint has its own response and most `post` requests will respond with `true` if successful.
 
 ```js
 browser.runtime.sendMessage(SIDE_ID, payload).then((response) => {

docs/api/plugins/playback.md

@@ -6,7 +6,7 @@ sidebar_label: Playback
 
 The Playback API is for the playback capabilities of Selenium IDE.  
 
-It is prefix with `/playback`.  
+It is prefixed with `/playback`.  
 
 ### `GET /playback/location`
 

docs/api/plugins/popup.md

@@ -4,7 +4,7 @@ title: Plugins Popup API
 sidebar_label: Popup
 ---
 
-The Popup API deals with popups that the user can see.  
+The Popup API deals with popups which the user can see.  
 
 This API is prefix with `/popup`.  
 

docs/api/plugins/record.md

@@ -4,13 +4,13 @@ title: Plugins Record API
 sidebar_label: Record
 ---
 
-Record API concerns with the recording capabilities of Selenium IDE.  
+The Record API is concerned with the recording capabilities of Selenium IDE.  
 
 This API is prefix with `/record`.  
 
 ### `GET /record/tab`
 
-Gets the `tabId` that the recorder is currently attached to (can be used even if not recording atm).
+Gets the `tabId` that the recorder is currently attached to (can be used even if not currently recording).
 
 ```js
 {

docs/api/plugins/system.md

@@ -4,19 +4,19 @@ title: Plugins System API
 sidebar_label: System
 ---
 
-The System API is the most basic API Selenium IDE provides. It is not prefixed and can be called with `/`. 
+The System API is the most basic API which Selenium IDE provides. It is not prefixed and can be called with `/`. 
 
 ### `GET /health`
 
 Used for plugin health checks, see [Plugin Health Checks](../../plugins/health-checks).
 
 ### `POST /register`
 
-Used to register your plugin with Selenium IDE, this way the IDE knows of your existence, see [registering the plugin](../../plugins/plugins-getting-started#registering-the-plugin).
+Used to register your plugin with Selenium IDE, this way the IDE knows of your plugin's existence, see [registering the plugin](../../plugins/plugins-getting-started#registering-the-plugin).
 
 ### `POST /log`
 
-Used for `system` logs, meaning when that the user can filter by system logs group.  
+Used for `system` logs, meaning when the user can filter by system logs group.  
 Logs that explain plugin usage, or status should be logged here.  
 
 ```js

docs/introduction/command-line-runner.md

@@ -37,11 +37,11 @@ Once everything's installed, running your tests is a simple matter of calling `s
 
 _NOTE: If you have multiple `.side` files you can use a wildcard (e.g., `/path/to/*.side`)._
 
-When you run this command it will launch your tests in parallel, in multiple browser windows, spread across `n` processes (where `n` is the number of available cores on your machine).
+When you run this command it will launch your tests in parallel, in multiple browser windows, spread across `n` processes (where `n` is the number of available CPU cores on your machine).
 
 The number of processes is configurable (amongst other things) at run time through various arguments you can provide.
 
-__NOTE: Parallel execution happens automically at the suite level. If you want the tests within a suite to be executed in parallel there is a setting you'll need to change. See [Test Parallelization In A Suite](command-line-runner.md#test-parallelization-in-a-suite) for details.__
+__NOTE: Parallel execution happens atomically at the suite level. If you want the tests within a suite to be executed in parallel, there is a setting you'll need to change. See [Test Parallelization In A Suite](command-line-runner.md#test-parallelization-in-a-suite) for details.__
 
 ## Run-time configuration
 
@@ -75,17 +75,17 @@ When running on a Grid you will likely want to control how many parallel session
 selenium-side-runner -w 10 --server http://localhost:4444/wd/hub
 ```
 
-The runner will automatically set the number of workers to the amount of cores available on your computer. In most cases this is the best option.
+The runner will automatically set the number of workers to the same number of CPU cores available on your computer. In most cases this is the best option.
 
 ### Chrome specific capabilities
 
-If you had Chrome installed in a non-standard location on your machine you could specify it so ChromeDriver knows where to look.
+If you have Chrome installed in a non-standard location on your machine you can specify the path so ChromeDriver knows where to look.
 
 ```sh
 selenium-side-runner -c "chromeOptions.binary='/path/to/non-standard/Chrome/install'"
 ```
 
-With Chrome specific capabilities you could also run the tests headlessly.
+With Chrome specific capabilities you can also run the tests headlessly.
 
 ```sh
 selenium-side-runner -c "chromeOptions.args=[disable-infobars, headless]"
@@ -113,7 +113,7 @@ selenium-side-runner --filter smoke
 
 ### Specify a default configuration
 
-Rather than remembering all of the command-line arguments you need (which can become unwieldy) there's the ability to store your run-time parameters in a configuration file.
+Rather than remembering all of the command-line arguments you need (which can become unwieldy), you have the ability to store your run-time parameters in a configuration file.
 
 There are two kinds of configuration files that you can use.
 
@@ -142,7 +142,7 @@ __NOTE: When using the `--config-file` flag, the `.side.yml` will be ignored.__
 
 ## Selenium IDE Configuration
 
-### Test Parallelization In A Suite
+### Test parallelization in a suite
 
 Out of the box, the runner executes suites in parallel, but tests within a suite are executed sequentially.
 
@@ -156,7 +156,7 @@ To run tests in a given suite in parallel, you'll need to update the settings fo
 
 To configure more than one suite to run this way, repeat steps 1-4 in each suite. Be sure to save the project file once you're done.
 
-## Advanced Options
+## Advanced options
 
 ### Additional params
 
@@ -174,7 +174,7 @@ selenium-side-runner --params "a='example-value'"
 
 #### Nested parameters
 
-Parameters can also be nested using a dot-notation.
+Parameters can also be nested using dot-notation.
 
 ```sh
 selenium-side-runner --params "a.b='another example-value'"
@@ -202,7 +202,7 @@ You can pass proxy capabilities to the browser using the following options in th
 
 #### Direct proxy  
 
-This options configures WebDriver to bypass all browser proxies.
+This option configures WebDriver to bypass all browser proxies.
 
 ##### From the command-line:
 
@@ -294,4 +294,4 @@ proxyType: system
 
 ### Code export
 
-If you're trying to learn how translate recorded tests into WebDriver code, or if you want to integrate recorded tests into an existing custom test framework, then what you need is code export which is on the project roadmap and will be available soon.
+If you're trying to learn how to translate recorded tests into WebDriver code, or if you want to integrate recorded tests into an existing custom test framework, then what you need is code export which is on the project roadmap and will be available soon.

docs/introduction/control-flow.md

@@ -6,13 +6,13 @@ sidebar_label: Control Flow
 
 Selenium IDE comes with commands that enable you to add conditional logic and looping to your tests.
 
-This enables you to execute commands (or a set of commands) only when certain conditions in your application are met. Or execute command(s) repeatedly based on pre-defined criteria.
+This enables you to execute commands (or a set of commands) only when certain conditions in your application are met, or execute command(s) repeatedly based on pre-defined criteria.
 
 ## JavaScript Expressions
 
 Conditions in your application are checked by using JavaScript expressions.
 
-You can use the `execute script` or `execute async script` commands to run a snippet of JavaScript at any point during your test and store the result in a variable. These variable can be used in a control flow command.
+You can use the `execute script` or `execute async script` commands to run a snippet of JavaScript at any point during your test and store the result in a variable. These variables can be used in a control flow command.
 
 You can also use JavaScript expressions directly in the control flow commands.
 

docs/introduction/faq.md

@@ -6,7 +6,7 @@ sidebar_label: Frequently Asked Questions
 
 ### How do I record hovers?
 
-Mouse over (a.k.a. hover) actions are difficult to automatically capture as part of a record cycle.
+Mouseover (a.k.a. hover) actions are difficult to automatically capture as part of a record cycle.
 
 To add a hover to your test, there's a small bit of manual intervention required. And there are two different ways you can do it.
 
@@ -44,7 +44,7 @@ There are certain circumstances where the built in wait strategies in the IDE ar
 
 ### How to install the IDE behind strict Proxy/Firewall?
 
-In situations you may not have full public internet access (such as behind a "Corporate Proxy or Firewall"). In those environments you will need to obtain a copy of the built Selenium IDE ZIP file in order to record automated test scripts. This is available on GitHub's "Releases" section here:
+In some situations you may not have full public internet access (such as behind a "Corporate Proxy or Firewall"). In those environments you will need to obtain a copy of the built Selenium IDE ZIP file in order to record automated test scripts. This is available on GitHub's "Releases" section here:
 
 https://github.com/SeleniumHQ/selenium-ide/releases
 

docs/introduction/getting-started.md

@@ -10,7 +10,7 @@ Install Selenium IDE from either the <a href="https://chrome.google.com/webstore
 
 ## Launch the IDE
 
-Once installed, launch it be clicking its icon from the menu bar in your browser.
+Once installed, launch it by clicking its icon from the menu bar in your browser.
 
 ### Troubleshooting
 
@@ -31,16 +31,17 @@ The extension might be enabled but the icon is hidden. Try resizing the menu bar
 
 In Chrome, you can do this by clicking to the right of the address bar, holding the click, and dragging it left or right.
 
-In Firefox you need right-click, click `Customize`, make adjustments to the menu bar, and click `Done`.
+In Firefox you need to right-click, click `Customize`, make adjustments to the menu bar, and click `Done`.
 
 ## Welcome Screen
 
 Upon launching the IDE you will be presented with a welcome dialog.
 
-This will give you quick access the following options:
+This will give you quick access to the following options:
 
-- Create a new project and start recording
+- Record a new test in a new project
 - Open an existing project
+- Create a new project
 - Close the IDE
 
 If this is your first time using the IDE (or you are starting a new project), then select the first option.
@@ -49,7 +50,7 @@ If this is your first time using the IDE (or you are starting a new project), th
 
 After creating a new project you will be prompted to name it and then asked to provide a base URL. The base URL is the URL of the application you are testing. It's something you set once and it gets used across all of the tests in this project. You can change it later if need-be.
 
-After completing these settings a new browser window will open, load the base URL, and start recording.
+After completing these settings, a new browser window will open, load the base URL, and start recording.
 
 Interact with the page and each of your actions will be recorded in the IDE. To stop recording, switch to the IDE window and click the recording icon.
 
@@ -65,7 +66,7 @@ Once added you can either input commands manually, or click the record icon in t
 
 Tests can be grouped together into suites.
 
-On project creation a `Default Suite` gets created and your first test gets added to it automatically.
+On project creation, a `Default Suite` gets created and your first test gets added to it automatically.
 
 To create and manage suites go to the `Test suites` panel. You can get there by clicking the drop-down at the top of the left side-bar menu (e.g., click on the word `Tests`) and selecting `Test suites`.
 
@@ -75,7 +76,7 @@ To add a suite, click the `+` symbol at the top of the left side-bar menu to the
 
 #### Add a test
 
-To add a test to a suite hover over the suite name, do the following:
+To add a test to a suite hover over the suite name, then do the following:
 
 1. Click on the icon that appears to the right of the `Test Suites` heading
 2. Click `Add tests`
@@ -96,7 +97,7 @@ To rename a suite hover over the suite name, click the icon that appears to the
 
 To save everything you've just done in the IDE, click the save icon in the top-right corner of the IDE.
 
-It will prompt you to for a location and name of where to save the project. The end result is a single file with an extension ending in `.side`.
+It will prompt you to for a location and name of where to save the project. The end result is a single file with a `.side` extension.
 
 ## Playback
 

docs/plugins/adding-commands.md

@@ -6,7 +6,7 @@ sidebar_label: Adding Commands
 
 To add a command to Selenium IDE firstly make sure to declare it in the [manifest](plugins-getting-started#the-manifest).
 
-After declaring the command Selenium IDE will expect you to respond to requests for it's execution and emission.  
+After declaring the command, Selenium IDE will expect you to respond to requests for it's execution and emission.  
 
 ## Executing a Command
 
@@ -44,7 +44,7 @@ Command details the user has input in the table:
 
 Playback options, detailing the execution environment:
 
-- `runId` - optional, a unique identifier for the current test run, can be used to infer certain commands were ran in the same run.
+- `runId` - optional, a unique identifier for the current test run, can be used to infer certain commands were performed during the same run.
 - `testId` - a persistent unique identifier for a test, even though the test's content may change, the same identifier will always be sent.
 - `frameId` - `integer` or `0 || undefined` indicates under which frame the command should be executed, `0` or `undefined` indicates that the command should be executed at the `window` level.
 - `tabId` - the tab to execute the command in.
@@ -96,9 +96,9 @@ In order to run the test case using the [command-line runner](../introduction/co
 
 Failing to provide it will result in the user getting an error when trying to save the test case.  
 
-Before implementing the command's code emitting, getting a general concept with how emitting works is a good idea ([link](emitting-code.md)).  
+Before implementing the command's code emitting, it will be useful to understand the general concepts of how emitting works ([link](emitting-code.md)).  
 
-This article only concerns the command's test code, if your plugin needs to add setup and teardown code, see [Emitting Setup and Teardown Code](emitting-setup-teardown.md).  
+This article is only concerned with the command's test code, if your plugin needs to add setup and teardown code, see [Emitting Setup and Teardown Code](emitting-setup-teardown.md).  
 
 Selenium IDE will send a request to emit the commands you've registered in the manifest.
 
@@ -127,7 +127,7 @@ Command details the user has input in the table:
 
 ### Returning the Emitted Code
 
-Once you've finished creating the JavaScript string to execute the command send it back to the IDE.  
+Once you've finished creating the JavaScript string to execute the command, send it back to the IDE.  
 
 **Don't use the `return` keyword, if you need to wait on a Promise use `await`, `return` will cause the test to quit early.**