docs: update Cypress branding (cypress-io#4583)

Author: elylucas

Diff for: .textlintrc

@@ -10,9 +10,7 @@
         // Cypress product
         ["^Cypress\.io", "Cypress"],
         ["Cypress' ", "Cypress's "],
-        ["the command log", "the Command Log"],
         ["Cypress dashboard", "Cypress Dashboard"],
-        ["test runner", "Test Runner"],
 
         // Brands and Technologies
         ["ansi", "ANSI"],

Diff for: content/api/commands/fixture.md

@@ -289,8 +289,8 @@ describe('User page', () => {
 ### Loaded just once
 
 Please keep in mind that fixture files are assumed to be unchanged during the
-test, and thus the Cypress App loads them just once. Even if you overwrite the
-fixture file itself, the already loaded fixture data remains the same.
+test, and thus Cypress loads them just once. Even if you overwrite the fixture
+file itself, the already loaded fixture data remains the same.
 
 If you wish to dynamically change the contents of a file during your tests,
 consider [`cy.readFile()`](/api/commands/readFile) instead.

Diff for: content/api/commands/intercept.md

@@ -1453,7 +1453,7 @@ cy.intercept('/users?_limit=+(3|5)')
 Under the hood, `cy.intercept` uses the [minimatch](/api/utilities/minimatch)
 library with the `{ matchBase: true }` option applied for glob matching and
 provides access to it via the `Cypress` global. This enables you to test your
-pattern in your spec or in the Cypress App browser console.
+pattern in your spec or in the Cypress browser console.
 
 You can invoke the `Cypress.minimatch` with just two arguments - the URL
 (`string`) and the pattern (`string`), respectively - and if it yields `true`,

Diff for: content/api/commands/invoke.md

@@ -156,7 +156,7 @@ Our input field
 <input type="text" name="text" data-cy="my-text-input" />
 ```
 
-The Cypress Test with `cy.invoke()` awaiting the promise:
+The Cypress test with `cy.invoke()` awaiting the promise:
 
 ```javascript
 function disableElementAsync(element) {

Diff for: content/api/commands/mount.md

@@ -6,7 +6,7 @@ componentSpecific: true
 <CtBetaAlert></CtBetaAlert>
 
 Cypress does not have a built-in `cy.mount()` command. The command must be set
-up in your support file. By default, when you use the Cypress app to
+up in your support file. By default, when you use Cypress to
 [configure](guides/component-testing/component-framework-configuration#Automatic-Configuration-Recommended)
 your project, one will be automatically scaffolded for you.
 

Diff for: content/api/commands/request.md

@@ -327,8 +327,8 @@ cy
 #### Request is not displayed in the Network Tab of Developer Tools
 
 Cypress does not _actually_ make an XHR request from the browser. We are
-actually making the HTTP request from the Cypress App (in Node). So, you won't
-see the request inside of your Developer Tools.
+actually making the HTTP request from Cypress (in Node). So, you won't see the
+request inside of your Developer Tools.
 
 ### CORS
 

Diff for: content/api/commands/screenshot.md

@@ -652,14 +652,14 @@ Once created, a session for a given `id` is cached for the duration of the spec
 file. You can't modify a stored session after it has been cached, but you can
 always create a new session with a different `id`.
 
-In order to reduce development time, when running the Cypress App in "open"
-mode, sessions will be cached _for spec file reruns_.
+In order to reduce development time, when running Cypress in "open" mode,
+sessions will be cached _for spec file reruns_.
 
 ### Explicitly clearing sessions
 
-When running the Cypress App in "open" mode, you can explicitly clear all
-sessions and re-run the spec file by clicking the "Clear All Sessions" button in
-the [Instrument Panel](#The-Instrument-Panel).
+When running Cypress in "open" mode, you can explicitly clear all sessions and
+re-run the spec file by clicking the "Clear All Sessions" button in the
+[Instrument Panel](#The-Instrument-Panel).
 
 <DocsImage src="/img/api/session/sessions-panel.png" alt="Sessions Instrument Panel" ></DocsImage>
 

Diff for: content/api/commands/session.md

@@ -52,7 +52,7 @@ If the `baseUrl` has not been set, you will need to specify a fully qualified
 URL or Cypress will attempt to act as your web server. See the
 [prefixes notes](#Prefixes) for more details.
 
-**Note:** visiting a new domain requires the Cypress App window to reload. You
+**Note:** visiting a new domain requires the Cypress window to reload. You
 cannot visit different super domains in a single test.
 
 **<Icon name="angle-right"></Icon> options** **_(Object)_**

Diff for: content/api/commands/visit.md

@@ -127,8 +127,8 @@ if (window.Cypress) {
 }
 ```
 
-The Cypress App can wait for the property `window.appReady` to be `true` before
-every test
+Cypress can wait for the property `window.appReady` to be `true` before every
+test
 
 ```js
 // spec.cy.js
@@ -145,8 +145,8 @@ beforeEach(() => {
 [This blog post](https://www.cypress.io/blog/2018/02/05/when-can-the-test-start/)
 explains how to use `cy.window()` to spy on the DOM `prototype` to detect when
 the application starts adding event listeners to the DOM elements. When this
-happens for the first time, the Cypress App knows that the application under
-test has started and the tests can begin.
+happens for the first time, Cypress knows that the application under test has
+started and the tests can begin.
 
 See
 [Set flag to start tests](https://glebbahmutov.com/blog/set-flag-to-start-tests/)
@@ -187,8 +187,8 @@ it('test', (done) => {
 It fails. But the interesting thing is that the type of `event` is
 `KeyboardEvent` when you `console.log(event)`.
 
-It's because the Cypress App uses an `iframe` to load the application under
-test. In other words, the `KeyboardEvent` used in the the code above and the
+It's because Cypress uses an `iframe` to load the application under test. In
+other words, the `KeyboardEvent` used in the the code above and the
 `KeyboardEvent` class from which the `event` variable is constructed are
 different `KeyboardEvent`s.
 

Diff for: content/api/commands/window.md

@@ -12,18 +12,18 @@ Cypress.browser // returns browser object
 
 The object has the following properties:
 
-| Property       | Type      | Description                                                                 |
-| -------------- | --------- | --------------------------------------------------------------------------- |
-| `channel`      | `string`  | Release channel of the browser, such as `stable`, `dev`, or `canary`.       |
-| `displayName`  | `string`  | Human-readable display name for the browser.                                |
-| `family`       | `string`  | Rendering engine being used. `chromium` or `firefox`.                       |
-| `isChosen`     | `boolean` | Whether the browser is selected in the browser selector of the Cypress App. |
-| `majorVersion` | `number`  | The major version number of the browser.                                    |
-| `name`         | `string`  | Machine-friendly name, like `chrome`, `electron`, or `firefox`.             |
-| `path`         | `string`  | Path to the browser on disk. Blank for Electron.                            |
-| `version`      | `string`  | Full version.                                                               |
-| `isHeadless`   | `boolean` | Whether the browser is running headlessly.                                  |
-| `isHeaded`     | `boolean` | Whether the browser displays headed.                                        |
+| Property       | Type      | Description                                                           |
+| -------------- | --------- | --------------------------------------------------------------------- |
+| `channel`      | `string`  | Release channel of the browser, such as `stable`, `dev`, or `canary`. |
+| `displayName`  | `string`  | Human-readable display name for the browser.                          |
+| `family`       | `string`  | Rendering engine being used. `chromium` or `firefox`.                 |
+| `isChosen`     | `boolean` | Whether the browser is selected in the browser selector of Cypress.   |
+| `majorVersion` | `number`  | The major version number of the browser.                              |
+| `name`         | `string`  | Machine-friendly name, like `chrome`, `electron`, or `firefox`.       |
+| `path`         | `string`  | Path to the browser on disk. Blank for Electron.                      |
+| `version`      | `string`  | Full version.                                                         |
+| `isHeadless`   | `boolean` | Whether the browser is running headlessly.                            |
+| `isHeaded`     | `boolean` | Whether the browser displays headed.                                  |
 
 ## Examples
 

Diff for: content/api/cypress-api/browser.md

@@ -453,7 +453,7 @@ For more complex use cases feel free to overwrite existing commands.
 
 If you are typing into a password field, the password input is masked
 automatically within your application. But [.type()](/api/commands/type)
-automatically logs any typed content into the Cypress App's Command Log.
+automatically logs any typed content into the Cypress Command Log.
 
 ```js
 cy.get('#username').type('[email protected]')
@@ -465,7 +465,7 @@ cy.get('#password').type('superSecret123')
 You may want to mask some values passed to the [.type()](/api/commands/type)
 command so that sensitive data does not display in screenshots or videos of your
 test run. This example overwrites the [.type()](/api/commands/type) command to
-allow you to mask sensitive data in the Cypress App's Command Log.
+allow you to mask sensitive data in the Cypress Command Log.
 
 ```js
 Cypress.Commands.overwrite('type', (originalFn, element, text, options) => {
@@ -489,7 +489,7 @@ cy.get('#username').type('[email protected]')
 cy.get('#password').type('superSecret123', { sensitive: true })
 ```
 
-Now our sensitive password is not printed to the Cypress App's Command Log when
+Now our sensitive password is not printed to the Cypress Command Log when
 `sensitive: true` is passed as an option to [.type()](/api/commands/type).
 
 <DocsImage src="/img/api/custom-commands/custom-command-type-masked-password.png"></DocsImage>