lint

cypress-io · Apr 12, 2023 · b6b4ad3 · b6b4ad3
1 parent 55956c6
commit b6b4ad3
Show file tree

Hide file tree

Showing 11 changed files with 11 additions and 11 deletions.
diff --git a/docs/guides/references/best-practices/assigning-return-values.mdx b/docs/guides/references/best-practices/assigning-return-values.mdx
@@ -58,4 +58,4 @@ If you're familiar with Cypress commands already, but find yourself using
   `beforeEach`.
 
 For working with either of these patterns, please read our
-[Variables and Aliases guide](/guides/core-concepts/variables-and-aliases).
+[Variables and Aliases guide](/guides/core-concepts/variables-and-aliases).
diff --git a/docs/guides/references/best-practices/before-and-after-hooks.mdx b/docs/guides/references/best-practices/before-and-after-hooks.mdx
@@ -202,4 +202,4 @@ could also interact directly with your database with direct queries, custom
 libraries, etc. If you already have non-JavaScript methods of handling or
 interacting with your database, you can use [`cy.exec`](/api/commands/exec),
 instead of [`cy.task`](/api/commands/task), to execute any system command or
-script.
+script.
diff --git a/docs/guides/references/best-practices/global-base-url.mdx b/docs/guides/references/best-practices/global-base-url.mdx
@@ -99,4 +99,4 @@ We also display an error if your server is not running at the specified
 ### Usage of `baseUrl` in depth
 
 This [short video](https://www.youtube.com/watch?v=f5UaXuAc52c) explains in
-depth how to use `baseUrl` correctly.
+depth how to use `baseUrl` correctly.
diff --git a/docs/guides/references/best-practices/intelligent-tests.mdx b/docs/guides/references/best-practices/intelligent-tests.mdx
@@ -19,4 +19,4 @@ Using a combination of [parallelization](/guides/guides/parallelization),
 [Auto Cancellation](/guides/cloud/smart-orchestration#Auto-Cancellation), and
 [Spec Prioritization](/guides/cloud/smart-orchestration#Spec-Prioritization),
 Smart Orchestration maximizes your available compute resources & minimizes
-waste.
+waste.
diff --git a/docs/guides/references/best-practices/organizing-tests.mdx b/docs/guides/references/best-practices/organizing-tests.mdx
@@ -38,4 +38,4 @@ We have several
 [Logging in recipes](https://github.com/cypress-io/cypress-example-recipes#logging-in-recipes)
 in our examples.
 
-:::
+:::
diff --git a/docs/guides/references/best-practices/selecting-elements.mdx b/docs/guides/references/best-practices/selecting-elements.mdx
@@ -162,4 +162,4 @@ package to use the familiar testing library methods (like `findByRole`,
 `findByLabelText`, etc...) to select elements in Cypress specs.
 
 In particular, if you're looking for more resources to understand how we
-recommend you approach testing your components, look to:
+recommend you approach testing your components, look to:
diff --git a/docs/guides/references/best-practices/test-responsibility.mdx b/docs/guides/references/best-practices/test-responsibility.mdx
@@ -86,4 +86,4 @@ describe('my form', () => {
       .and('have.value', 'Johnny')
   })
 })
-```
+```
diff --git a/docs/guides/references/best-practices/test-state.mdx b/docs/guides/references/best-practices/test-state.mdx
@@ -130,4 +130,4 @@ test and ensuring nothing in previous tests leaks into subsequent ones.
 
 We're also paving the way to make it less complicated to write multiple tests
 against the "default" state of the form. That way each test stays lean but each
-can be run independently and pass.
+can be run independently and pass.
diff --git a/docs/guides/references/best-practices/uneccessary-waiting.mdx b/docs/guides/references/best-practices/uneccessary-waiting.mdx
@@ -74,4 +74,4 @@ cy.intercept('GET', '/users', [{ name: 'Maggy' }, { name: 'Joan' }]).as(
 cy.get('[data-testid="fetch-users"]').click()
 cy.wait('@getUsers') // <--- wait explicitly for this route to finish
 cy.get('table tr').should('have.length', 2)
-```
+```
diff --git a/docs/guides/references/best-practices/visiting-external-sites.mdx b/docs/guides/references/best-practices/visiting-external-sites.mdx
@@ -155,4 +155,4 @@ email's functionality and visual style:
    exposes an API to read off emails. You will then need the proper
    authentication credentials, which your server could provide, or you could use
    environment variables. Some email services already provide
-   [Cypress plugins](/plugins#Email) to access emails.
+   [Cypress plugins](/plugins#Email) to access emails.
diff --git a/docs/guides/references/best-practices/web-servers.mdx b/docs/guides/references/best-practices/web-servers.mdx
@@ -48,4 +48,4 @@ Start your web server before running Cypress and kill it after it completes.
 Are you trying to run in CI?
 
 We have
-[examples showing you how to start and stop your web server](/guides/continuous-integration/introduction#Boot-your-server).
+[examples showing you how to start and stop your web server](/guides/continuous-integration/introduction#Boot-your-server).