cypress-io · jennifer-shehane · Nov 8, 2024 · Nov 8, 2024 · Nov 8, 2024 · Nov 8, 2024
diff --git a/docs/accessibility/core-concepts/accessibility-score.mdx b/docs/accessibility/core-concepts/accessibility-score.mdx
@@ -13,7 +13,7 @@ Cypress produces a top-line percentage score that indicates a general sense of a
 
 The severity levels presented in Cypress Cloud match the Axe Core® `impact` level for each rule. This impact classification was developed by the creators of Axe, Deque Systems, to aid in prioritization of accessibility results, by highlighting rules that are likely to reveal the most substantial barriers (such as missing label text) so they can be addressed first.
 
-It's important to note that the Web Content Accessibility Guidelines (WCAG) standards do not have a concept of relative severity of the Success Criteria. For **compliance** purposes, all failures of the Success Criteria count and must be addressed. For **usability** purposes, however, the impact values provided by Axe Core® provide excellent guidance about which issues to take up first to bring the most benefit to disabled users of your plaform as quickly as possible.
+It's important to note that the Web Content Accessibility Guidelines (WCAG) standards do not have a concept of relative severity of the Success Criteria. For **compliance** purposes, all failures of the Success Criteria count and must be addressed. For **usability** purposes, however, the impact values provided by Axe Core® provide excellent guidance about which issues to take up first to bring the most benefit to disabled users of your platform as quickly as possible.
 
 ## Algorithm
 

diff --git a/docs/accessibility/core-concepts/inspecting-violation-details.mdx b/docs/accessibility/core-concepts/inspecting-violation-details.mdx
@@ -37,7 +37,7 @@ Each element can be clicked to pin an example of that element in the UI and reve
 
 ### Snapshots
 
-Note: these are not images or screenshots from the tests. They are fully hydrated HTML and CSS snapshots of your application. This makes it easy to see what each violation represents in context, as well as inspect the entire DOM, make adjustments and see how things appear in the browser's accessibility tree. This makes a big difference in understanding and debugging issues, because you don't have to run the application locally to reproduce the state, and with access to the full DOM you can understand even complex issues and idenfity solutions.
+Note: these are not images or screenshots from the tests. They are fully hydrated HTML and CSS snapshots of your application. This makes it easy to see what each violation represents in context, as well as inspect the entire DOM, make adjustments and see how things appear in the browser's accessibility tree. This makes a big difference in understanding and debugging issues, because you don't have to run the application locally to reproduce the state, and with access to the full DOM you can understand even complex issues and identify solutions.
 
 This area also has the Test Replay button to provide access to any tests where this snapshot appeared, as well as the specific URL of the snapshot displayed at the bottom of the screen.
 

diff --git a/docs/api/cypress-api/iscy.mdx b/docs/api/cypress-api/iscy.mdx
@@ -5,7 +5,7 @@ title: Cypress.isCy
 `Cypress.isCy()` checks if a variable is a valid instance of `cy` or a `cy`
 chainable.
 
-This utility may be useful when writing a pluging using [Node Events](/api/node-events/overview)
+This utility may be useful when writing a plugin using [Node Events](/api/node-events/overview)
 for Cypress and you want to determine if a value is a valid Cypress chainable.
 
 ## Syntax

diff --git a/docs/app/component-testing/custom-frameworks.mdx b/docs/app/component-testing/custom-frameworks.mdx
@@ -8,7 +8,7 @@ sidebar_position: 100
 ##### <Icon name="question-circle" color="#4BBFD2" /> What you'll learn
 
 - How to customize Cypress to support your favorite framework
-- How to create a custom Framwork Definition and Mount Adapter for your framework
+- How to create a custom Framework Definition and Mount Adapter for your framework
 - How to test and publish your custom framework
 
 :::
@@ -70,7 +70,7 @@ When configuring a project to use Component Testing, Cypress will load any
 dependencies following this naming convention from the project's `node_modules`
 and present them as framework options.
 
-A simple example of a Framework Defintion for the
+A simple example of a Framework Definition for the
 [Solid.js](https://www.solidjs.com/) library is shown below. We generally
 recommend naming this `definition.cjs`. In our
 [official template](https://github.com/cypress-io/cypress-ct-definition-template),

diff --git a/docs/app/continuous-integration/overview.mdx b/docs/app/continuous-integration/overview.mdx
@@ -355,7 +355,7 @@ You can see the total available machine memory and the current free memory by
 running the [`cypress info`](https://on.cypress.io/command-line#cypress-info)
 command.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 npx cypress info

diff --git a/docs/app/guides/authentication-testing/azure-active-directory-authentication.mdx b/docs/app/guides/authentication-testing/azure-active-directory-authentication.mdx
@@ -27,7 +27,7 @@ React, Angular, or Vue.
 
 For this guide, we are mainly going to focus on setting up Cypress to test
 against an Azure Active Directory web app. Please clone the
-[Microsoft Identity Javascript Tutorial](https://github.com/Azure-Samples/ms-identity-javascript-tutorial/tree/c1956b658efa331bb5df11a0038ad32d12dad3ce/1-Authentication/1-sign-in)
+[Microsoft Identity JavaScript Tutorial](https://github.com/Azure-Samples/ms-identity-javascript-tutorial/tree/c1956b658efa331bb5df11a0038ad32d12dad3ce/1-Authentication/1-sign-in)
 and follow the steps to set up your application.
 
 Once set up, you'll need to modify a few things in the `App/index.html` file:

diff --git a/docs/app/guides/authentication-testing/okta-authentication.mdx b/docs/app/guides/authentication-testing/okta-authentication.mdx
@@ -11,7 +11,7 @@ description: 'Implement Okta authentication in Cypress end-to-end testing. Ensur
 ##### <Icon name="question-circle" color="#4BBFD2" /> What you'll learn
 
 - How to test Okta authentication in Cypress
-- How to set Okta redentials in Cypress
+- How to set Okta credentials in Cypress
 - How to adapt an Okta app for testing
 
 :::

diff --git a/docs/app/guides/cypress-studio.mdx b/docs/app/guides/cypress-studio.mdx
@@ -95,7 +95,7 @@ describe('Cypress Studio Demo', () => {
 
 #### Step 1 - Run the spec
 
-We 'll use Cypress Studio to perform a "New Transaction" user journey. First,
+We'll use Cypress Studio to perform a "New Transaction" user journey. First,
 launch Cypress and select **End To End testing**, then choose a browser to run specs
 in.
 

diff --git a/docs/app/references/assertions.mdx b/docs/app/references/assertions.mdx
@@ -82,7 +82,7 @@ entire list of available BDD Chai assertions [here](http://chaijs.com/api/bdd/).
 | decrease(_function_) <br /><small>**Aliases:** decreases</small>                          | `.should('decrease', obj, 'val')`<br />`expect(fn).to.decrease(obj, 'val')`                                                                                                                                            |
 
 These getters are also available for BDD assertions. They don't actually do
-anything, but they enable you to write clear, english sentences.
+anything, but they enable you to write clear, English sentences.
 
 | Chainable getters                                                                           |
 | ------------------------------------------------------------------------------------------- |

diff --git a/docs/app/references/command-line.mdx b/docs/app/references/command-line.mdx
@@ -755,7 +755,7 @@ Prints information about Cypress and the current environment such as:
 - Operating system information.
 - System memory including free space.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 cypress info
@@ -832,7 +832,7 @@ In most cases the binary and the package versions will be the same, but they
 could be different if you have installed a different version of the package and
 for some reason failed to install the matching binary version.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 cypress version
@@ -844,7 +844,7 @@ Bundled Node version: 16.16.0
 
 You can print each individual component's version number also.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 cypress version --component package
@@ -879,7 +879,7 @@ Print all existing installed versions of Cypress. The output will be a table
 with cached versions and the last time the binary was used by the user,
 determined from the file's access time.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 cypress cache list
@@ -896,7 +896,7 @@ You can calculate the size of every Cypress version folder by adding the
 `--size` argument to the command. Note that calculating the disk size can be
 slow.
 
-{/* hack: using css language label to respect decimals in syntax highlightng */}
+{/* hack: using css language label to respect decimals in syntax highlighting */}
 
 ```css
 cypress cache list --size

diff --git a/docs/app/references/configuration.mdx b/docs/app/references/configuration.mdx
@@ -306,7 +306,7 @@ especially useful in
 working locally. This gives you the ability to change configuration options
 without modifying any code or build scripts.
 
-For example, these enviroment variables in the command line will override any
+For example, these environment variables in the command line will override any
 `viewportWidth` or `viewportHeight` options set in the Cypress configuration:
 
 ```shell

diff --git a/docs/app/references/environment-variables.mdx b/docs/app/references/environment-variables.mdx
@@ -198,7 +198,7 @@ values are converted to `Number` or `Boolean` wherever possible.
 
 :::
 
-For example, these enviroment variables in the command line will override any
+For example, these environment variables in the command line will override any
 `viewportWidth` or `viewportHeight` options set in the Cypress configuration:
 
 ```shell

diff --git a/docs/app/references/error-messages.mdx b/docs/app/references/error-messages.mdx
@@ -48,7 +48,7 @@ the purpose of utility functions.
 
 ### <Icon name="exclamation-triangle" color="red" /> Error Loading Config
 
-The `supportFile` configuration option was removed from the root configutation
+The `supportFile` configuration option was removed from the root configuration
 object in Cypress version `10.0.0`. Instead, it must be added within each
 testing type's configuration object as a separate property if you would like to
 use a file other than the default

diff --git a/docs/cloud/features/analytics/enterprise-reporting.mdx b/docs/cloud/features/analytics/enterprise-reporting.mdx
@@ -121,7 +121,7 @@ These are some of the questions that will be answered by the data presented on t
 The **Flaky Tests** tab on Enterprise Reporting allows you to see flaky test occurrences and rates for your entire organization or
 specific projects. This can be a single snapshot based on the start and end date filters, or can be viewed over time. Flake
 _rate_ can be helpful because it allows you to see what % of runs in a project are flaky. This allows easy comparison of flaky
-tests between projects regardless of the volume of runs occuring in the projects.
+tests between projects regardless of the volume of runs occurring in the projects.
 
 <DocsImage
   src="/img/cloud/features/analytics/enterprise-reporting-flaky-tests.png"

diff --git a/docs/cloud/features/branch-review.mdx b/docs/cloud/features/branch-review.mdx
@@ -166,7 +166,7 @@ Navigating into the test detail view reveals a side-by-side comparison of the te
 
 3. Test Replay and artifacts
 
-4. Test attempts (decending order)
+4. Test attempts (descending order)
 
 5. Code change diffs
 

diff --git a/docs/cloud/features/test-replay.mdx b/docs/cloud/features/test-replay.mdx
@@ -264,7 +264,7 @@ so your issue may already be fixed.
 
 :::
 
-If you're experiencing an issue and have already tried the troublshooting steps below,
+If you're experiencing an issue and have already tried the troubleshooting steps below,
 you can report an issue within the Test Replay window in the Cloud by clicking the **Report an Issue** button.
 
 <DocsImage

diff --git a/docs/cloud/integrations/data-extract-api.mdx b/docs/cloud/integrations/data-extract-api.mdx
@@ -566,7 +566,7 @@ https://cloud.cypress.io/enterprise-reporting/report?token=YOUR-API-KEY&report_i
 
 ### Flaky rate per project
 
-This report allows you to understand the flaky _rate_ occuring in your projects, not just the _count_ of flaky tests.
+This report allows you to understand the flaky _rate_ occurring in your projects, not just the _count_ of flaky tests.
 Sometimes a high flake count is seen simply because the test runs very frequently, but the % of flake could be lower than in
 other tests that run less often. The flaky rate per project is calculated for the time period requested. Flaky rate is shown
 as a whole number. For example: 1 flaky test over 4 runs has a flaky rate of 25.
@@ -585,7 +585,7 @@ https://cloud.cypress.io/enterprise-reporting/report?token=YOUR-API-KEY&report_i
 
 ### Flaky rate per project over time
 
-This report allows you to understand the flaky _rate_ occuring in your projects, not just the _count_ of flaky tests.
+This report allows you to understand the flaky _rate_ occurring in your projects, not just the _count_ of flaky tests.
 Sometimes a high flake count is seen simply because the test runs very frequently, but the % of flake could be lower than in
 other tests that run less often. The flaky rate per project is calculated for the time period requested. Flaky rate is shown
 as a whole number. For example: 1 flaky test over 4 runs has a flaky rate of 25.

diff --git a/docs/cloud/integrations/slack.mdx b/docs/cloud/integrations/slack.mdx
@@ -19,7 +19,7 @@ sidebar_label: Slack
 
 Cypress's Slack integration provides real-time results for your Cypress tests, all in one place - improving remote
 collaboration and giving wider visibility into test failures and flake, [UI Coverage](/ui-coverage/get-started/introduction),
-and [Cypress Accesibility](/accessibility/get-started/introduction) results.
+and [Cypress Accessibility](/accessibility/get-started/introduction) results.
 
 The Cypress integration for Slack allows you to:
 

diff --git a/docs/cloud/integrations/teams.mdx b/docs/cloud/integrations/teams.mdx
@@ -73,7 +73,7 @@ workspace.
      width={1000}
    />
 
-5. You'll naviagte to a window that manages webhooks as a way for Cypress Cloud
+5. You'll navigate to a window that manages webhooks as a way for Cypress Cloud
    to communicate with Microsoft Teams. First, you must configure an _Incoming
    Webhook_ to a Teams channel.
 
@@ -167,7 +167,7 @@ needs. You can have Cypress Cloud post run results for a specific project.
    />
 4. Scroll down and click **Add Teams webhook** in the **Microsoft Teams**
    section.
-5. You'll naviagte to a window that manages webhooks as a way for Cypress Cloud
+5. You'll navigate to a window that manages webhooks as a way for Cypress Cloud
    to communicate with Microsoft Teams. First, you must configure an _Incoming
    Webhook_ to a Teams channel.
 

diff --git a/docs/ui-coverage/core-concepts/interactivity.mdx b/docs/ui-coverage/core-concepts/interactivity.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Testing interative elements | Cypress UI Coverage'
+title: 'Testing interactive elements | Cypress UI Coverage'
 description: 'UI Coverage uses a set of rules, based on HTML semantics, WHATWG standards, as well as some additional rules defined by Cypress, to determine which elements are interactive.'
 sidebar_label: Interactivity
 sidebar_position: 10

diff --git a/docs/ui-coverage/core-concepts/views.mdx b/docs/ui-coverage/core-concepts/views.mdx
@@ -19,4 +19,4 @@ UI Coverage uses certain default rules to generate a single view from dynamic UR
 - All hash parameters are removed, unless the hash parameter starts with a `/`, such as `#/admin`.
 - If there are multiple URLs that are exactly the same except for a different integer or UUID value in the same path parameter, then that path parameter is replaced with a wildcard (`*`).
 
-These rules can be overriden via [views](/ui-coverage/configuration/views) configuration.
+These rules can be overridden via [views](/ui-coverage/configuration/views) configuration.