remove v10 image references + unused images

docs/app/core-concepts/open-mode.mdx

@@ -391,14 +391,14 @@ it('intercept command log', () => {
 
 ## Preview pane
 
-The right-hand side of the Test Runner is where the Application or Component
+The right-hand side of the App is where the Application or Component
 Under Test is rendered.
 
 ### Application Under Test <E2EOnlyBadge />
 
 In
 [E2E Testing](/app/core-concepts/testing-types#What-is-E2E-Testing),
-the right-hand side of the Test Runner is used to display the Application Under
+the right-hand side of the App is used to display the Application Under
 Test (AUT): the application that was navigated to using a
 [`cy.visit()`](/api/commands/visit) or any subsequent routing calls made from
 the visited application.
@@ -407,7 +407,6 @@ In the example below, we wrote the following code in our test file:
 
 ```javascript
 cy.visit('https://example.cypress.io')
-
 cy.title().should('include', 'Kitchen Sink')
 ```
 
@@ -504,14 +503,14 @@ available for debugging.
   alt="Cypress app showing mounted component and password assertion"
 />
 
-The CUT also displays in the size and orientation specified in your tests. You
+The AUT also displays in the size and orientation specified in your tests. You
 can change the size or orientation with the
 [`cy.viewport()`](/api/commands/viewport) command or in your
-[Cypress configuration](/app/references/configuration#Viewport). If the CUT
+[Cypress configuration](/app/references/configuration#Viewport). If the AUT
 does not fit within the current browser window, it is scaled appropriately to
 fit within the window.
 
-The current size and scale of the CUT is displayed in the top right corner of
+The current size and scale of the AUT is displayed in the top right corner of
 the window.
 
 The image below shows that our application is displaying at `500px` width,
@@ -530,14 +529,6 @@ that prevent the tests from running.
   alt="Cypress app showing error as application under test"
 />
 
-:::caution
-
-Internally, the AUT renders within an iframe. This can sometimes cause
-unexpected behaviors
-[explained here.](/api/commands/window#Cypress-uses-2-different-windows)
-
-:::
-
 ## Selector Playground
 
 The Selector Playground is an interactive feature that helps you:

docs/app/end-to-end-testing/testing-your-app.mdx

@@ -101,7 +101,7 @@ touch cypress/e2e/home_page.cy.js
 Once that file is created, you should see it in the list of spec files.
 
 <DocsImage
-  src="/img/app/get-started/e2e/v10/testing-your-app-home-page-spec.png"
+  src="/img/app/get-started/e2e/testing-your-app-home-page-spec.png"
   alt="List of files including home_page.cy.js"
   width="75%"
 />
@@ -129,7 +129,7 @@ it('successfully loads', () => {
 -->
 
 <DocsImage
-  src="/img/app/get-started/e2e/v10/testing-your-app-visit-fail.png"
+  src="/img/app/get-started/e2e/testing-your-app-visit-fail.png"
   alt="Error in Cypress showing cy.visit failed"
   width="75%"
 />

docs/app/end-to-end-testing/writing-your-first-end-to-end-test.mdx

@@ -93,7 +93,7 @@ see Cypress display the suite, the test and your first assertion (which should
 be passing in green).
 
 <DocsImage
-  src="/img/app/get-started/e2e/v10/first-test.png"
+  src="/img/app/get-started/e2e/first-test.png"
   alt="My first test shown passing in Cypress"
 />
 
@@ -136,7 +136,7 @@ describe('My First Test', () => {
 -->
 
 <DocsImage
-  src="/img/app/get-started/e2e/v10/first-test-failing.png"
+  src="/img/app/get-started/e2e/first-test-failing.png"
   alt="Failing test"
 />
 
@@ -274,7 +274,7 @@ describe('My First Test', () => {
 -->
 
 <DocsImage
-  src="/img/app/get-started/e2e/v10/first-test-failing-contains.png"
+  src="/img/app/get-started/e2e/first-test-failing-contains.png"
   alt="Test failing to not find content 'hype'"
 />
 

docs/app/guides/cross-browser-testing.mdx

@@ -29,7 +29,7 @@ system or CI environment. A full list of detected browsers is displayed within
 the browser selection menu of [Cypress](/app/core-concepts/open-mode).
 
 <DocsImage
-  src="/img/app/cross-browser-testing/v10/browser-select-FF.png"
+  src="/img/app/cross-browser-testing/browser-select-FF.png"
   alt="Cypress with Firefox selected as the browser"
 />
 

docs/app/guides/network-requests.mdx

@@ -211,7 +211,7 @@ When you use [`cy.intercept()`](/api/commands/intercept) to define a route,
 Cypress displays this under "Routes" in the Command Log.
 
 <DocsImage
-  src="/img/app/network-requests/v10/server-routing-table.png"
+  src="/img/app/network-requests/server-routing-table.png"
   alt="Routing Table"
 />
 
@@ -433,7 +433,7 @@ it('test', () => {
 -->
 
 <DocsImage
-  src="/img/app/network-requests/v10/clear-source-of-failure.png"
+  src="/img/app/network-requests/clear-source-of-failure.png"
   alt="Wait Failure"
 />
 

docs/app/guides/test-retries.mdx

@@ -92,7 +92,7 @@ Assuming we have configured test retries with **2** retry attempts (for a total
    will mark the test as failed and then move on to run any remaining tests.
 
 <DocsImage
-  src="/img/app/test-retries/v10/attempt-3-fail.png"
+  src="/img/app/test-retries/attempt-3-fail.png"
   alt="Test retries attempt 3 fail"
 />
 

docs/app/references/configuration.mdx

@@ -460,7 +460,7 @@ highlighted to show where the value has been set via the following ways:
 - [setupNodeEvents](#setupNodeEvents)
 
 <DocsImage
-  src="/img/app/configuration/v10/see-resolved-configuration.png"
+  src="/img/app/configuration/see-resolved-configuration.png"
   alt="See resolved configuration"
 />
 
@@ -529,7 +529,7 @@ send a `503` status code. As a convenience it also sets a
 matched.
 
 <DocsImage
-  src="/img/app/references/v10/blocked-host.png"
+  src="/img/app/references/blocked-host.png"
   alt="Network tab of dev tools showing blocked host"
 />
 

docs/app/references/launching-browsers.mdx

@@ -53,7 +53,7 @@ Cypress automatically detects available browsers on your OS. You can switch the
 browser by using the drop down near the top right corner:
 
 <DocsImage
-  src="/img/app/launching-browsers/v10/browser-list-dropdown.png"
+  src="/img/app/launching-browsers/browser-list-dropdown.png"
   alt="Select a different browser"
 />
 
@@ -398,7 +398,7 @@ Once selected, the Brave browser is detected using the same approach as any
 other browser of the `chromium` family.
 
 <DocsImage
-  src="/img/app/launching-browsers/v10/brave-running-tests.png"
+  src="/img/app/launching-browsers/brave-running-tests.png"
   alt="Brave browser executing end-to-end tests"
 />
 
@@ -478,7 +478,7 @@ You might notice that if you already have the browser open you will see two of
 the same browser icons in your dock.
 
 <DocsImage
-  src="/img/app/launching-browsers/v10/multiple-chrome-icons.png"
+  src="/img/app/launching-browsers/multiple-chrome-icons.png"
   alt="Cypress icon with 2 Google Chrome icons"
 />
 
@@ -495,7 +495,7 @@ Cypress look different than regular sessions. You'll see a darker theme around
 the chrome of the browser. You'll always be able to visually distinguish these.
 
 <DocsImage
-  src="/img/app/launching-browsers/v10/cypress-browser-chrome.png"
+  src="/img/app/launching-browsers/cypress-browser-chrome.png"
   alt="Cypress Browser with darker chrome"
 />
 

docs/cloud/account-management/data-storage-and-masking.mdx

@@ -174,7 +174,7 @@ Users can mask passwords in the Cypress Command Log by using a custom command li
 Cypress allows users to block requests from specified hosts. [See our blockHosts configuration guide.](/app/references/configuration#blockHosts)
 
 <DocsImage
-  src="/img/app/references/v10/blocked-host.png"
+  src="/img/app/references/blocked-host.png"
   alt="Network tab of dev tools showing blocked host"
 />