Merge pull request #5139 from cypress-io/collected-updates

Collected updates

Author: jaffrepaul

docs/faq/questions/cloud-faq.mdx

@@ -6,8 +6,9 @@ hide_table_of_contents: true
 ## <Icon name="angle-right" /> What is Cypress Cloud?
 
 <DocsImage
-  src="/img/dashboard/dashboard-runs-list.png"
+  src="/img/guides/cloud/runs/run-details-page.png"
   alt="Cloud Screenshot"
+  width="80%"
 />
 
 [Cypress Cloud](https://on.cypress.io/cloud) gives you access to tests you've
@@ -32,7 +33,7 @@ Please see our [Pricing Page](https://www.cypress.io/pricing) for more details.
 ## <Icon name="angle-right" /> What counts as a test result?
 
 Which [pricing tier](https://www.cypress.io/pricing) is best for you depends on
-the number of test you record each month in your organization.
+the number of tests you record each month in your organization.
 
 Tests are recorded when [cypress run](/guides/guides/command-line#cypress-run)
 is called with the `--record` flag while supplying the record `--key`. This
@@ -57,9 +58,9 @@ been invited to see and review the test results of your organization.
 ## <Icon name="angle-right" /> What is the difference between public and private projects?
 
 **A public project** means that anyone can see the recorded runs for it. It's
-similar to how public projects on Github, Travis, or Circle are handled. Anyone
-who knows your `projectId` will be able to see the recorded runs, screenshots,
-and videos for public projects.
+similar to how public projects on Github, Travis, or CircleCI are handled.
+Anyone who knows your `projectId` will be able to see the recorded runs,
+screenshots, and videos for public projects.
 
 **A private project** means that only [users](/guides/cloud/users) you
 explicitly invite to your [organization](/guides/cloud/organizations) can see
@@ -72,8 +73,8 @@ Cypress is **complementary** to your
 [CI provider](/guides/continuous-integration/introduction), and plays a
 completely different role.
 
-It doesn't replace or change anything related to CI. You will run Cypress tests
-in your CI provider.
+It doesn't replace or change anything related to CI. You will still run Cypress
+tests in your CI provider.
 
 The difference between [Cypress Cloud](/guides/cloud/introduction) and your CI
 provider is that your CI provider has no idea what is going on inside of the
@@ -160,8 +161,8 @@ Find a variable across your containers that is the same for all of them, but is
 different from run to run. For example it could be an environment variable
 called `CI_RUN_ID` that you set when creating the containers to run Cypress. You
 can pass this variable via CLI argument
-[`--ci-build-id`](/guides/guides/command-line#cypress-run-ci-build-id-lt-id-gt)when
-starting Cypress in each container:
+[`--ci-build-id`](/guides/guides/command-line#cypress-run-ci-build-id-lt-id-gt)
+when starting Cypress in each container:
 
 ```shell
 cypress run --record --parallel --ci-build-id $CI_RUN_ID
@@ -215,13 +216,7 @@ by:
 4. Review your organization's usage
 5. Scroll down and select **Upgrade** under your plan of choice
 
-## <Icon name="angle-right" /> I'm working at a restrictive VPN. Which subdomains do I have to allow on
-
-my VPN for Cypress Cloud to work properly?
-
-To send the data and results of your tests to
-[Cypress Cloud](https://on.cypress.io/cloud-introduction), Cypress needs free
-access to some URLs.
+## <Icon name="angle-right" /> I'm working at a restrictive VPN. Which subdomains do I have to allow on my VPN for Cypress Cloud to work properly?
 
 If you are running the tests from within a restrictive VPN you will need to
 allow some URLs so that Cypress can have effective communication with Cypress

docs/faq/questions/company-faq.mdx

@@ -20,6 +20,4 @@ Yes! You can check our open positions and apply
 ## <Icon name="angle-right" /> Why the name _Cypress_?
 
 We believe that tests should always pass -- in other words, should always be
-green. A cypress is an evergreen tree. So, Cypress!
-
-<Icon name="tree" color="green" />
+green. A cypress is an evergreen tree. So, Cypress! 🌲

docs/guides/cloud/jira-integration.mdx

@@ -24,7 +24,7 @@ workflow to enable:
 
 ## Installing the Jira integration
 
-1. Visit **Integrations → Jira** in Cypress Cloud and click "Install Jira" {' '}
+1. Visit **Integrations → Jira** in Cypress Cloud and click "Install Jira"
    <DocsImage
      src="/img/dashboard/jira-integration/dashboard-jira-integration-install.png"
      alt="Cypress Cloud Integrations"
@@ -65,7 +65,7 @@ workflow to enable:
      alt="Cypress Cloud Select Organization for Jira Integration"
    />
 1. The Jira Integration is complete. A list of projects permitted is provided on
-   the Jira Integration page. {' '}
+   the Jira Integration page.
    <DocsImage
      src="/img/dashboard/jira-integration/dashboard-jira-integration-completed.png"
      alt="Cypress Cloud Jira Integration"

docs/guides/cloud/organizations.mdx

@@ -201,7 +201,7 @@ Organization to set up SSO.
 #### Enable SSO
 
 1. Log in to Cypress Cloud and navigate to the **Integrations** page for your
-   organization. {' '}
+   organization.
    <DocsImage
      src="/img/dashboard/organizations/integrations-nenu-screenshot.png"
      alt="Enable SSO"
@@ -265,7 +265,7 @@ below, refer to
    Cypress Cloud needs the information provided here:
 
 - Copy the Identity Provider Single sign-on URL to Cypress Cloud.
-- Download the certificate and upload that to Cypress Cloud. {' '}
+- Download the certificate and upload that to Cypress Cloud.
   <DocsImage
     src="/img/dashboard/organizations/okta-download-certificate-for-cypress-dashboard.png"
     alt="Download Certificate"

docs/guides/component-testing/angular/overview.mdx

@@ -32,9 +32,7 @@ npx cypress open
 <DocsImage
   src="/img/guides/component-testing/select-test-type.jpg"
   caption="Choose Component Testing"
->
-  {' '}
-</DocsImage>
+/>
 
 The Cypress Launchpad will guide you through configuring your project.
 

docs/guides/component-testing/react/api.mdx

@@ -117,7 +117,7 @@ it('mounts', () => {
     <td>strict</td>
     <td>boolean (optional)</td>
     <td>
-      Render component in React{' '}
+      Render component in React
       <a href="https://reactjs.org/docs/strict-mode.html">strict mode</a>
       It activates additional checks and warnings for child components.
     </td>
@@ -139,7 +139,7 @@ Type that the `mount` function yields
     <td>component</td>
     <td>React.ReactNode</td>
     <td>
-      Render component in React{' '}
+      Render component in React
       <a href="https://reactjs.org/docs/strict-mode.html">strict mode</a>
       It activates additional checks and warnings for child components.
     </td>

docs/guides/component-testing/react/overview.mdx

@@ -38,9 +38,7 @@ npx cypress open
 <DocsImage
   src="/img/guides/component-testing/select-test-type.jpg"
   caption="Choose Component Testing"
->
-  {' '}
-</DocsImage>
+/>
 
 The Cypress Launchpad will guide you through configuring your project.
 

docs/guides/component-testing/svelte/overview.mdx

@@ -42,9 +42,7 @@ npx cypress open
 <DocsImage
   src="/img/guides/component-testing/select-test-type.jpg"
   caption="Choose Component Testing"
->
-  {' '}
-</DocsImage>
+/>
 
 The Cypress Launchpad will guide you through configuring your project.
 

docs/guides/component-testing/vue/overview.mdx

@@ -36,9 +36,7 @@ npx cypress open
 <DocsImage
   src="/img/guides/component-testing/select-test-type.jpg"
   caption="Choose Component Testing"
->
-  {' '}
-</DocsImage>
+/>
 
 The Cypress Launchpad will guide you through configuring your project.
 

docs/guides/core-concepts/test-isolation.md renamed to docs/guides/core-concepts/test-isolation.mdx

@@ -35,26 +35,28 @@ command's documentation.
 To run a command, you'll need to prefix each command in order to properly locate
 the cypress executable.
 
+(requires [email protected] or greater)
+
 ```
-$(npm bin)/cypress run
+npx cypress run
 ```
 
-...or...
+...or by using Yarn...
 
 ```
-./node_modules/.bin/cypress run
+yarn cypress run
 ```
 
-...or... (requires [email protected] or greater)
+...or...
 
 ```
-npx cypress run
+$(npm bin)/cypress run
 ```
 
-...or by using Yarn...
+...or...
 
 ```
-yarn cypress run
+./node_modules/.bin/cypress run
 ```
 
 You may find it easier to add the cypress command to the `scripts` object in

docs/guides/guides/command-line.mdx

@@ -120,7 +120,7 @@ do that no other testing framework can:
   or videos of your entire test suite when run from the CLI. Record to
   [Cypress Cloud](/guides/cloud/introduction) to store them with your test
   results for zero-configuration debugging.
-- **Cross browser Testing:** Run tests within Firefox and Chrome-family browsers
+- **Cross Browser Testing:** Run tests within Firefox and Chrome-family browsers
   (including Edge and Electron) locally and
   [optimally in a Continuous Integration pipeline](/guides/guides/cross-browser-testing).
 - **Smart Orchestration:** Once you're set up to record to Cypress Cloud, easily

docs/guides/overview/why-cypress.mdx

@@ -290,7 +290,7 @@ If you're familiar with Cypress commands already, but find yourself using
 For working with either of these patterns, please read our
 [Variables and Aliases guide](/guides/core-concepts/variables-and-aliases).
 
-## Visiting external sites
+## Visiting External Sites
 
 :::danger
 
@@ -447,7 +447,7 @@ email's functionality and visual style:
    environment variables. Some email services already provide
    [Cypress plugins](/plugins#Email) to access emails.
 
-## Having tests rely on the state of previous tests
+## Having Tests Rely On The State Of Previous Tests
 
 :::danger
 
@@ -578,7 +578,7 @@ 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.
 
-## Creating "tiny" tests with a single assertion <E2EOnlyBadge />
+## Creating "Tiny" Tests With A Single Assertion <E2EOnlyBadge />
 
 :::danger
 
@@ -664,7 +664,7 @@ describe('my form', () => {
 })
 ```
 
-## Using `after` or `afterEach` hooks
+## Using `after` Or `afterEach` Hooks
 
 :::danger
 
@@ -1011,7 +1011,7 @@ 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).
 
-## Setting a global baseUrl
+## Setting a Global `baseUrl`
 
 :::danger
 

docs/guides/references/best-practices.mdx

@@ -280,7 +280,7 @@ For this test, we will add a new bank account. Our interactions are as follows:
      src="/img/guides/cypress-studio/add-test-form-complete.png"
      alt="Cypress Studio Add Test Complete Bank Account Form"
    />
-4. Click the "Save" button {' '}
+4. Click the "Save" button
    <DocsImage
      src="/img/guides/cypress-studio/add-test-form-save.png"
      alt="Cypress Studio Add Test Save Bank Account"

docs/guides/references/cypress-studio.mdx

@@ -33,6 +33,14 @@ div.markdown {
     }
   }
 
+  // add border bottom to code tags that are in a link
+  a:has(> code) {
+    border-bottom: 1px dotted var(--ifm-link-color);
+    &:hover {
+      border-bottom: 1px solid var(--ifm-link-color);
+    }
+  }
+
   h2 {
     margin-bottom: 1.5rem;
     padding-bottom: 0.5rem;