Update small things on website (#380)

* Update the_selenium_project_and_tools.en.md

Small spelling fix

* Update on_test_automation.en.md

Small format change

* Update types_of_testing.en.md

Small spelling and formatting changes

* Update installing_webdriver_binaries.en.md

Minor grammar

* Update installing_standalone_server.en.md

Minor language

* Update browsers.en.md

Harmonize spelling

* Update locating_elements.en.md

Minor grammar

* Update _index.en.md

Minor language

* Update understanding_the_components.en.md

Consistency with other locations

* Update driver_requirements.en.md

Clearer language

* Update driver_requirements.en.md

Minor changes

* Update browser_manipulation.en.md

Minor changes for clarity

* Update waits.en.md

Minor change

* Update js_alerts_prompts_and_confirmations.en.md

Change message to plural

* Update web_element.en.md

Make complete sentence

* Update keyboard.en.md

Make complete sentence

* Update remote_webdriver_server.en.md

Clarify language

* Update remote_webdriver_client.en.md

Update first sentence

* Update _index.en.md

Move a period for small grammar change

* Update page_object_models.en.md

Add footnote to explain acronym

* Update domain_specific_language.en.md

* Update page_object_models.en.md

Add extra letter missing in the last commit for this page

* Update generating_application_state.en.md

Add footnote and change word to plural

* Update improved_reporting.en.md

Add some links

* Update avoid_sharing_state.en.md

Add bullets to list

* Update test_independency.en.md

Change colon to period

* Harmonize syntax and fixing some minor things

* Update docs_source_files/content/getting_started_with_webdriver/locating_elements.en.md

Co-Authored-By: Diego Molina <diemol@users.noreply.github.com>

* Update docs_source_files/content/support_packages/mouse_and_keyboard_actions_in_detail.en.md

Co-Authored-By: Diego Molina <diemol@users.noreply.github.com>

* Update docs_source_files/content/webdriver/browser_manipulation.en.md

Co-Authored-By: Diego Molina <diemol@users.noreply.github.com>

* Update links in all languages

Author: Gunnar Johansson

docs_source_files/content/getting_started/html-runner.en.md

@@ -13,8 +13,8 @@ campatible tools.
 * Combination of releases of geckodriver / firefox /
 selenium-html-runner matters. There might be a software
 compatibility matrix somewhere.
-* selenium-html-runner runs only Test Suite (not Test Case - what
-is for example an export from Monitis Transaction Monitor). Be
+* selenium-html-runner runs only Test Suite (not Test Case - 
+for example an export from Monitis Transaction Monitor). Be
 sure you comply with this.
 * For Linux users with no DISPLAY - you need to start html-runner
 with Virtual display (search for xvfb)

docs_source_files/content/getting_started/quick.en.md

@@ -43,7 +43,7 @@ Selenium IDE can be used to generate _quick and dirty_
 Java, Python, and Ruby). Given the maintainability of code generated
 through Selenium IDE, it is not recommended to use it for anything
 more than getting acquainted with element locators or generating
-_throw away code_. We're sure that once you get used to the
+_throw away code_. We are sure that once you get used to the
 WebDriver API, you will never use Selenium IDE.
 
 

docs_source_files/content/getting_started_with_webdriver/browsers.en.md

@@ -15,7 +15,7 @@ The Selenium framework officially supports the following browsers:
 | Opera | Opera [Chromium](//github.com/operasoftware/operachromiumdriver/) / [Presto](//github.com/operasoftware/operaprestodriver) | 10.5 and newer |
 | Safari | [Apple](//webkit.org/blog/6900/webdriver-support-in-safari-10/) | 10 and newer |
 
-## Specialised browsers
+## Specialized browsers
 
 There is also a set of specialized browsers out there
 typically used in development environments.
@@ -24,4 +24,4 @@ and Selenium ties in support for the following specialized drivers:
 
 | Driver Name | Purpose | Maintainer |
 | -------- | ---------- | ------------------ |
-| HtmlUnitDriver | Headless browser emulator backed by Rhino | Selenium project |
+| HtmlUnitDriver | Headless browser emulator backed by Rhino | Selenium project |

docs_source_files/content/getting_started_with_webdriver/locating_elements.en.md

@@ -105,7 +105,7 @@ const cheddar = await driver.findElement(By.css('#cheese #cheddar'));
 
 ### Locating multiple elements
 
-It's possible that the document we are working with may turn out to have an
+It is possible that the document we are working with may turn out to have an
 ordered list of the cheese we like the best:
 
 ```html
@@ -122,7 +122,7 @@ to have to retrieve each of the items individually, a superior
 technique for retrieving cheese is to make use of the pluralized
 version `findElements(By)`. This method returns a collection of web
 elements. If only one element is found, it will still return a
-collection (of one element). If no elements match the locator, an
+collection (of one element). If no element matches the locator, an
 empty list will be returned.
 
 {{< code-tab >}}
@@ -168,7 +168,7 @@ that comes with complicated DOM traversals.
 If unique IDs are unavailable, a well-written CSS selector is the
 preferred method of locating an element. XPath works as well as CSS
 selectors, but the syntax is complicated and frequently difficult to
-debug. Though XPath selectors are very flexible, they're typically
+debug. Though XPath selectors are very flexible, they are typically
 not performance tested by browser vendors and tend to be quite slow.
 
 Selection strategies based on link text and partial link text have

docs_source_files/content/grid/_index.en.md

@@ -15,13 +15,13 @@ one server acts as the hub that routes JSON formatted test commands
 to one or more registered Grid nodes.
 Tests contact the hub to obtain access to remote browser instances.
 The hub has a list of registered servers that it provides access to,
-and allows us to control these instances.
+and allows control of these instances.
 
 Selenium Grid allows us to run tests in parallel on multiple machines,
 and to manage different browser versions and browser configurations centrally
 (instead of in each individual test).
 
-Selenium Grid isn't a silver bullet.
+Selenium Grid is not a silver bullet.
 It solves a subset of common delegation and distribution problems,
-but will for example not manage your infrastructure
+but will for example not manage your infrastructure,
 and might not suit your specific needs.

docs_source_files/content/grid/components_of_a_grid.en.md

@@ -11,22 +11,22 @@ weight: 2
 * Takes instructions from client and executes them remotely on the nodes
 * Manages threads
 
-A _Hub_ is a central point where all your tests are sent to.
+A _Hub_ is a central point where all your tests are sent.
 Each Selenium Grid consists of exactly one hub. The hub needs to be reachable
 from the respective clients (i.e. CI server, Developer machine etc.)
 The hub will connect one or more nodes
 that tests will be delegated to.
 
 ## Nodes
 
-* This is where the browsers live
+* Where the browsers live
 * Registers itself to the hub and communicates its capabilities
 * Receives requests from the hub and executes them
 
 _Nodes_ are different Selenium instances
 that will execute tests on individual computer systems.
 There can be many nodes in a grid.
-The machines which are nodes need do not need to be the same platform
+The machines which are nodes do not need to be the same platform
 or have the same browser selection as that of the hub or the other nodes.
 A node on Windows might have the capability of
 offering Internet Explorer as a browser option,

docs_source_files/content/grid/purposes_and_main_functionalities.en.md

@@ -5,7 +5,7 @@ weight: 1
 ---
 
 * Central entry point for all tests
-* Management and control of the nodes / environment where the browsers run on
+* Management and control of the nodes / environment where the browsers run
 * Scaling
 * Running tests in parallel
 * Cross platform testing

docs_source_files/content/grid/setting_up_your_own_grid.en.md

@@ -21,7 +21,7 @@ complete with its own node infrastructure.
 
 This example will show you how to start the Selenium 2 Grid Hub,
 and register both a WebDriver node and a Selenium 1 RC legacy node.
-We’ll also show you how to call the grid from Java.
+We will also show you how to call the grid from Java.
 The hub and nodes are shown here running on the same machine,
 but of course you can copy the selenium-server-standalone to multiple machines.
 
@@ -66,7 +66,7 @@ are possible command-line flags.
 
 You certainly can get by with only the simple command shown above,
 but if you need more advanced configuration,
-then you may also for convenience specify a JSON format config file
+you can also specify a JSON format config file, for convenience,
 to configure the hub when you start it.
 You can do it like so:
 
@@ -192,26 +192,26 @@ hub/node to be reachable from a different machine.
 #### Specifying the port
 
 The default TCP/IP port used by the hub is 4444. If you need to change the port 
-please use above mentioned configurations
+please use above mentioned configurations.
 
 ## Troubleshooting
 
 ### Using Log file
-For advance troubleshooting you can specify log file to log system messages.
-For that start Selenium GRID hub or node with -log argument. Please see the below example
+For advanced troubleshooting you can specify a log file to log system messages.
+Start Selenium GRID hub or node with -log argument. Please see the below example:
 
 ```shell
 java -jar selenium-server-standalone.jar -role hub -log log.txt
 ```
 
-Use your favorite text editor to open log file (log.txt in above example) to find 
+Use your favorite text editor to open log file (log.txt in the example above) to find 
 "ERROR" logs if you get issues.
 
 ### Using `-debug` argument
 
-Also you can use `-debug` argument to print debug logs on console.
-For that start Selenium Grid Hub or Node with `-debug` argument. Please see 
-the below example
+Also you can use `-debug` argument to print debug logs to console.
+Start Selenium Grid Hub or Node with `-debug` argument. Please see 
+the below example:
 
 ```shell
 java -jar selenium-server-standalone.jar -role hub -debug
@@ -223,11 +223,12 @@ The Selenium Grid must be protected from external access using appropriate
 firewall permissions.
 
 Failure to protect your Grid could result in one or more of the following occurring:
+
 * You provide open access to your Grid infrastructure
-* You allow 3rd parties to access internal web applications and files
-* You allow 3rd parties to run custom binaries
+* You allow third parties to access internal web applications and files
+* You allow third parties to run custom binaries
 
-See this blog post on [Detectify](//labs.detectify.com) which gives a good 
+See this blog post on [Detectify](//labs.detectify.com), which gives a good 
 overview of how a publicly exposed Grid could be misused: 
 [Don't Leave your Grid Wide Open](//labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/).
 
@@ -236,7 +237,7 @@ overview of how a publicly exposed Grid could be misused:
 [Docker](//www.docker.com/) provides a convenient way to
 provision and scale Selenium Grid infrastructure in a unit known as a container.
 Containers are standardised units of software that contain everything required
-to run the desired application including all dependencies in a reliable and repeatable
+to run the desired application, including all dependencies, in a reliable and repeatable
 way on different machines.
 
 The Selenium project maintains a set of Docker images which you can download

docs_source_files/content/guidelines_and_recommendations/_index.en.md

@@ -9,20 +9,20 @@ weight: 7
 
 A note on "Best Practices": We've intentionally avoided the phrase "Best
 Practices" in this documentation. No one approach works for all situations.
-We prefer the idea of "Guidelines and Recommendations." We encourage
+We prefer the idea of "Guidelines and Recommendations". We encourage
 you to read through these and thoughtfully decide what approaches
 will work for you in your particular environment.
 
 Functional testing is difficult to get right for many reasons.
-As if application state, complexity, and dependencies don't make testing difficult enough,
+As if application state, complexity, and dependencies do not make testing difficult enough,
 dealing with browsers (especially with cross-browser incompatibilities)
 makes writing good tests a challenge.
 
 Selenium provides tools to make functional user interaction easier,
-but doesn't help you write well-architected test suites.
+but does not help you write well-architected test suites.
 In this chapter we offer advice, guidelines, and recommendations.
 on how to approach functional web page automation.
 
 This chapter records software design patterns popular
 amongst many of the users of Selenium
-that have proven successful over the years.
+that have proven successful over the years.

docs_source_files/content/guidelines_and_recommendations/avoid_sharing_state.en.md

@@ -6,12 +6,12 @@ weight: 6
 Although mentioned in several places it is worth mentioning again. Ensure 
 tests are isolated from one another.
 
-Don't share test data. Imagine several tests that each query the database 
+* Do not share test data. Imagine several tests that each query the database 
 for valid orders before picking one to perform an action on. Should two tests
 pick up the same order you are likely to get unexpected behaviour.
 
-Clean up stale data in the application that might be picked up by another 
+* Clean up stale data in the application that might be picked up by another 
 test e.g. invalid order records.
 
-Create a new WebDriver instance per test. This helps ensure test isolation
+* Create a new WebDriver instance per test. This helps ensure test isolation
 and makes parallelisation simpler.

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.en.md

@@ -3,8 +3,8 @@ title: "Consider using a fluent API"
 weight: 8
 ---
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). Selenium already
+implements something like this in their `FluentWait` class, which is
 meant as an alternative to the standard <code>Wait</code> class. 
 You could enable the Fluent API design pattern in your page object 
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.es.md

@@ -9,8 +9,8 @@ English to Spanish. Do you speak Spanish? Help us to translate
 it by sending us pull requests!
 {{% /notice %}}
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). 
+Selenium already implements something like this in their `FluentWait` class which is
 meant as an alternative to the standard <code>Wait</code> class. 
 You could enable the Fluent API design pattern in your page object 
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.fr.md

@@ -9,8 +9,8 @@ English to French. Do you speak French? Help us to translate
 it by sending us pull requests!
 {{% /notice %}}
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). 
+Selenium already implements something like this in their `FluentWait` class which is
 meant as an alternative to the standard <code>Wait</code> class. 
 You could enable the Fluent API design pattern in your page object 
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.ja.md

@@ -8,8 +8,8 @@ weight: 8
 日本語は話せますか？プルリクエストをして翻訳を手伝ってください!
 {{% /notice %}}
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). 
+Selenium already implements something like this in their `FluentWait` class which is
 meant as an alternative to the standard <code>Wait</code> class.
 You could enable the Fluent API design pattern in your page object
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.nl.md

@@ -9,8 +9,8 @@ English to Dutch. Do you speak Dutch? Help us to translate
 it by sending us pull requests!
 {{% /notice %}}
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). 
+Selenium already implements something like this in their `FluentWait` class which is
 meant as an alternative to the standard <code>Wait</code> class. 
 You could enable the Fluent API design pattern in your page object 
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/consider_using_a_fluent_api.zh-cn.md

@@ -8,8 +8,8 @@ weight: 8
 您熟悉英语与简体中文吗？帮助我们翻译它，通过 pull requests 给我们！
 {{% /notice %}}
 
-Martin Fowler coined the term "Fluent API". Selenium already
-implements something like this in their `FluentWait` class which is
+Martin Fowler coined the term ["Fluent API"](//www.martinfowler.com/bliki/FluentInterface.html). 
+Selenium already implements something like this in their `FluentWait` class which is
 meant as an alternative to the standard <code>Wait</code> class.
 You could enable the Fluent API design pattern in your page object
 and then query the Google search page with a code snippet like this one:

docs_source_files/content/guidelines_and_recommendations/domain_specific_language.en.md

@@ -7,15 +7,15 @@ A domain specific language (DSL) is a system which provides the user with
 an expressive means of solving a problem. It allows a user to
 interact with the system on their terms – not just programmer-speak.
 
-Your users, in general, don't care how your site looks. They don't
+Your users, in general, do not care how your site looks. They do not
 care about the decoration, animations, or graphics. They
 want to use your system to push their new employees through the
-process with minimal difficulty.  They want to book travel to Alaska.
-They want to configure and buy unicorns at a discount. Your job as the
+process with minimal difficulty; they want to book travel to Alaska; 
+they want to configure and buy unicorns at a discount. Your job as
 tester is to come as close as you can to “capturing” this mind-set.
-With that in mind, we set about “modeling” the application you're
+With that in mind, we set about “modeling” the application you are
 working on, such that the test scripts (the user's only pre-release
-proxy) “speak” for and represent the user.
+proxy) “speak” for, and represent the user.
 
 With Selenium, DSL is usually represented by methods, written to make
 the API simple and readable – they enable a report between the
@@ -29,7 +29,7 @@ intelligence specialists, etc.).
 * **Extensible:** Functionality can (reasonably) be added
   without breaking contracts and existing functionality.
 * **Maintainable:** By leaving the implementation details out of test
-  cases, you are well-insulated against changes to the AUT (application under test).
+  cases, you are well-insulated against changes to the AUT*.
 
 
 ## Java
@@ -65,7 +65,7 @@ public AccountPage loginAsUser(String username, String password) {
 
 This method completely abstracts the concepts of input fields,
 buttons, clicking, and even pages from your test code. Using this
-approach, all your tester has to do is call this method. This gives
+approach, all a tester has to do is call this method. This gives
 you a maintenance advantage: if the login fields ever changed, you
 would only ever have to change this method - not your tests.
 
@@ -87,9 +87,11 @@ public void loginTest() {
 It bears repeating: one of your primary goals should be writing an
 API that allows your tests to address **the problem at hand, and NOT
 the problem of the UI**. The UI is a secondary concern for your
-users – they don't care about the UI, they just want to get their job
+users – they do not care about the UI, they just want to get their job
 done. Your test scripts should read like a laundry list of things
 the user wants to DO, and the things they want to KNOW. The tests
 should not concern themselves with HOW the UI requires you to go
 about it.
 
+***AUT**: Application under test
+

docs_source_files/content/guidelines_and_recommendations/generating_application_state.en.md

@@ -4,11 +4,13 @@ weight: 3
 ---
 
 Selenium should not be used to prepare a test case.  All repetitive
-actions, and preparation for a test case, should be done through other
+actions and preparations for a test case, should be done through other
 methods.  For example, most web UIs have authentication (e.g. a login
 form). Eliminating logging in via web browser before every test will
 improve both the speed and stability of the test. A method should be
-created to gain access to the AUT (e.g. using an API to login and set a
+created to gain access to the AUT* (e.g. using an API to login and set a
 cookie).  Also, creating methods to pre-load data for
 testing should not be done using Selenium.  As mentioned previously,
-existing APIs should be leveraged to create data for the AUT.
+existing APIs should be leveraged to create data for the AUT*.
+
+***AUT**: Application under test

docs_source_files/content/guidelines_and_recommendations/improved_reporting.en.md

@@ -10,4 +10,9 @@ reports that can generate xUnit or HTML formatted reports.  xUnit
 reports are popular for importing results to a Continuous Integration
 (CI) server like Jenkins, Travis, Bamboo, etc.  Here are some links
 for more information regarding report outputs for several languages.
-<!-- TODO: Add links.-->
+<!-- TODO: Add links.-->
+[NUnit 3 Console Runner](//github.com/nunit/docs/wiki/Console-Runner)
+[NUnit 3 Console Command Line](//github.com/nunit/docs/wiki/Console-Command-Line)
+[xUnit getting test results in TeamCity](//xunit.net/docs/getting-test-results-in-teamcity)
+[xUnit getting test results in CruiseControl.NET](//xunit.net/docs/getting-test-results-in-ccnet)
+[xUnit getting test results in Azure DevOps](//xunit.net/docs/getting-test-results-in-azure-devops)

docs_source_files/content/guidelines_and_recommendations/improved_reporting.es.md

@@ -16,4 +16,5 @@ reports that can generate xUnit or HTML formatted reports.  xUnit
 reports are popular for importing results to a Continuous Integration
 (CI) server like Jenkins, Travis, Bamboo, etc.  Here are some links
 for more information regarding report outputs for several languages.
-<!-- TODO: Add links.-->
+<!-- TODO: Add links.-->
+[NUnit 3 Console Runner](//github.com/nunit/docs/wiki/Console-Runner)