Bryan.lee/patch 4

content/en/tests/setup/junit_xml.md

@@ -11,9 +11,9 @@ further_reading:
     - link: "/continuous_integration/tests"
       tag: "Documentation"
       text: "Explore Test Results and Performance"
-    - link: "/continuous_integration/troubleshooting/"
+    - link: "/tests/troubleshooting/"
       tag: "Documentation"
-      text: "Troubleshooting CI Visibility"
+      text: "Troubleshooting Test Optimization"
 ---
 
 {{< site-region region="gov" >}}
@@ -235,7 +235,7 @@ See [Providing metadata with XPath expressions](#providing-metadata-with-xpath-e
 : Enable forwarding content from the XML reports as [Logs][6]. The content inside `<system-out>`, `<system-err>`, and `<failure>` is collected as logs. Logs from elements inside a `<testcase>` are automatically connected to the test.<br/>
 **Environment variable**: `DD_CIVISIBILITY_LOGS_ENABLED`<br/>
 **Default**: `false`<br/>
-**Note**: Logs are billed separately from CI Visibility.
+**Note**: Logs are billed separately from Test Optimization.
 
 `--max-concurrency`
 : The number of concurrent uploads to the API.<br/>
@@ -369,7 +369,7 @@ The JUnit XML uses a private [GitHub App][12] to read the `CODEOWNERS` file.
 3. Follow the instructions to configure the integration for a personal or organization account.
 4. In **Edit Permissions**, grant `Contents: Read` access.
 5. Click **Create App in GitHub** to finish the app creation process on GitHub.
-6. Give the app a name, for example, `Datadog CI Visibility`.
+6. Give the app a name, for example, `Datadog Test Optimization`.
 7. Click **Install GitHub App** and follow the instructions on GitHub.
 
 ### Manually providing the `test.source.file` tag

content/en/tests/setup/python.md

@@ -14,13 +14,13 @@ further_reading:
     - link: "/continuous_integration/tests"
       tag: "Documentation"
       text: "Explore Test Results and Performance"
-    - link: "/continuous_integration/troubleshooting/"
+    - link: "/tests/troubleshooting/"
       tag: "Documentation"
-      text: "Troubleshooting CI Visibility"
+      text: "Troubleshooting Test Optimization"
 ---
 
 {{< site-region region="gov" >}}
-<div class="alert alert-warning">CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
+<div class="alert alert-warning">Test Optimization is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
 ## Compatibility

content/en/tests/setup/ruby.md

@@ -14,13 +14,13 @@ further_reading:
     - link: "/continuous_integration/tests"
       tag: "Documentation"
       text: "Explore Test Results and Performance"
-    - link: "/continuous_integration/troubleshooting/"
+    - link: "/tests/troubleshooting/"
       tag: "Documentation"
-      text: "Troubleshooting CI Visibility"
+      text: "Troubleshooting Test Optimization"
 ---
 
 {{< site-region region="gov" >}}
-<div class="alert alert-warning">CI Visibility is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
+<div class="alert alert-warning">Test Optimization is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
 ## Compatibility
@@ -301,7 +301,7 @@ Alternatively, you can enable automatic instrumentation in `test_helper/spec_hel
 require "datadog/auto_instrument" if ENV["DD_ENV"] == "ci"
 ```
 
-**Note**: In CI mode, these traces are submitted to CI Visibility, and they do **not** show up in Datadog APM.
+**Note**: In CI mode, these traces are submitted to Test Optimization, and they do **not** show up in Datadog APM.
 
 For the full list of available instrumentation methods, see the [tracing documentation][6]
 
@@ -347,7 +347,7 @@ end
 
 ## Using manual testing API
 
-If you use RSpec, Minitest, or Cucumber, **do not use the manual testing API**, as CI Visibility automatically instruments them and sends the test results to Datadog. The manual testing API is **incompatible** with already supported testing frameworks.
+If you use RSpec, Minitest, or Cucumber, **do not use the manual testing API**, as Test Optimization automatically instruments them and sends the test results to Datadog. The manual testing API is **incompatible** with already supported testing frameworks.
 
 Use the manual testing API only if you use an unsupported testing framework or have a different testing mechanism.
 Full public API documentation is available on [YARD site][8].

content/en/tests/setup/swift.md

@@ -14,9 +14,9 @@ further_reading:
     - link: "/tests/test_impact_analysis/swift"
       tag: "Documentation"
       text: "Speed up your test jobs with Test Impact Analysis"
-    - link: "/continuous_integration/troubleshooting/"
+    - link: "/tests/troubleshooting/"
       tag: "Documentation"
-      text: "Troubleshooting CI Visibility"
+      text: "Troubleshooting Test Optimization"
 ---
 
 {{< site-region region="gov" >}}
@@ -731,7 +731,7 @@ Always call `module.end()` at the end so that all the test info is flushed to Da
 
 ## Best practices
 
-Follow these practices to take full advantage of the testing framework and CI Visibility.
+Follow these practices to take full advantage of the testing framework and Test Optimization.
 
 ### Generate symbols file when building