lint

Author: jaffrepaul

docs/api/actions/selectfile.mdx

@@ -50,8 +50,7 @@ cy.get('input[type=file]').selectFile('file contents')
 
 ### Arguments
 
-<Icon name="angle-right" /> **file _(String, Array, Object or
-Cypress.Buffer)_**
+<Icon name="angle-right" /> **file _(String, Array, Object or Cypress.Buffer)_**
 
 Either a single file, or an array of files. A file can be:
 

docs/api/assertions/should.mdx

@@ -239,9 +239,9 @@ cy.get('p').should(($p) => {
 })
 ```
 
-<Icon name="exclamation-triangle" color="red" /> **Warning** Any value returned
-from a `.should()` callback function will be ignored. The original subject will
-be yielded to the next command.
+<Icon name="exclamation-triangle" color="red" /> **Warning** Any value returned from
+a `.should()` callback function will be ignored. The original subject will be yielded
+to the next command.
 
 ```js
 cy.get('p')

docs/api/commands/wrap.mdx

@@ -151,9 +151,9 @@ For example, given the following example:
 - `bar()` is also dependent on some data that is created while after calling
   other Cypress commands.
 
-<Icon name="exclamation-triangle" color="red" />** If you wrap the
-asynchronous functions in `cy.wrap()`, then `bar()` may be called prematurely
-before the required data is available:
+<Icon name="exclamation-triangle" color="red" />
+** If you wrap the asynchronous functions in `cy.wrap()`, then `bar()` may be called
+prematurely before the required data is available:
 
 ```javascript
 cy.wrap(foo())
@@ -170,9 +170,9 @@ cy.wrap(bar()) // DON'T DO THIS
 This behavior is due to the function invocation `foo()` and `bar()`, which call
 the functions immediately to return a Promise.
 
-<Icon name="check-circle" color="green" />** If you want `bar()` to execute
-after `foo()` and the [cy.get()](/api/commands/get) commands, one solution is to
-chain off the final command using [.then()](/api/commands/then):
+<Icon name="check-circle" color="green" />
+** If you want `bar()` to execute after `foo()` and the [cy.get()](/api/commands/get)
+commands, one solution is to chain off the final command using [.then()](/api/commands/then):
 
 ```javascript
 cy.wrap(foo())

docs/api/cypress-api/custom-commands.mdx

@@ -847,8 +847,10 @@ couple commands.
 
 Don't do things like:
 
-- <Icon name="exclamation-triangle" color="red" />** `cy.clickButton(selector)`
-- <Icon name="exclamation-triangle" color="red" />** `.shouldBeVisible()`
+- <Icon name="exclamation-triangle" color="red" />
+  ** `cy.clickButton(selector)`
+- <Icon name="exclamation-triangle" color="red" />
+  ** `.shouldBeVisible()`
 
 This first custom command is wrapping `cy.get(selector).click()`. Going down
 this route would lead to creating dozens or even hundreds of custom commands to

docs/api/cypress-api/custom-queries.mdx

@@ -410,8 +410,10 @@ already quite expressive and powerful.
 
 Don't do things like:
 
-- <Icon name="exclamation-triangle" color="red" />** `cy.getButton()`
-- <Icon name="exclamation-triangle" color="red" />** `.getFirstTableRow()`
+- <Icon name="exclamation-triangle" color="red" />
+  ** `cy.getButton()`
+- <Icon name="exclamation-triangle" color="red" />
+  ** `.getFirstTableRow()`
 
 Both of these are wrapping `cy.get(selector)`. It's completely unnecessary. Just
 call `.get('button')` or `.get('tr:first')`.

docs/faq/questions/using-cypress-faq.mdx

@@ -1107,7 +1107,8 @@ hosted by Curiosity Software. In addition, since our
 
 <Icon name="github" inline="true" contentType="rwa" /> is implemented using XState
 model state library, we are looking for ways to make model-based testing simpler
-and more powerful. Read [Access XState from Cypress Test](https://glebbahmutov.com/blog/cypress-and-xstate/) for our start.
+and more powerful. Read [Access XState from Cypress Test](https://glebbahmutov.com/blog/cypress-and-xstate/)
+for our start.
 
 ### <Icon name="angle-right" /> Can Cypress test WASM code?
 

docs/guides/cloud/account-management/organizations.mdx

@@ -38,7 +38,7 @@ with Cypress teams.
 
 You can create an organization from within
 [Cypress Cloud](https://on.cypress.io/cloud) by opening the organization
-switcher and clicking <Icon name="plus" /> Create new organization**.
+switcher and clicking <Icon name="plus" /> Create new organization\*\*.
 
 <DocsImage
   src="/img/guides/cloud/organizations/create-org.jpg"

docs/guides/cloud/getting-started.mdx

@@ -31,9 +31,8 @@ can also record your tests when running locally.
 
 :::tip
 
-<Icon name="check-circle" color="green" /> Make sure to
-[install](/guides/getting-started/installing-cypress) and
-[open](/guides/getting-started/opening-the-app) the Cypress app to get started
+<Icon name="check-circle" color="green" /> Make sure to [install](/guides/getting-started/installing-cypress)
+and [open](/guides/getting-started/opening-the-app) the Cypress app to get started
 recording!
 
 :::

docs/guides/cloud/integrations/jira.mdx

@@ -72,7 +72,7 @@ workflow to enable:
    />
 
 :::caution
-   
+
 <Icon name="exclamation-triangle" /> Only one Active installation is supported
 
 :::

docs/guides/cloud/integrations/source-control/github.mdx

@@ -17,7 +17,8 @@ to use GitHub integration.
 
 :::caution
 
-<Icon name="exclamation-triangle" /> The user enabling the integration must be a GitHub admin to enable repository access.
+<Icon name="exclamation-triangle" /> The user enabling the integration must be a
+GitHub admin to enable repository access.
 
 :::