Updated based on reviewer comments

Author: ada

private-preview/aopt/aopt-scenarios.rst

@@ -32,8 +32,8 @@ To gain a comprehensive overview of all workloads and identify optimization oppo
    #. If the :guilabel:`Confidence level` at the top of the page is high, copy and paste the YAML snippets in :guilabel:`Instant Recommendations` into that workload's container configuration.
 
 
-What are some modifcations that I can make to improve efficiency and performance by right-sizing workloads based on actual usage metrics?
-==============================================================================================================================================================================
+How can I improve efficiency and performance by right-sizing workloads based on actual usage metrics?
+=========================================================================================================
 
 To see actual usage metrics for an individual workload:
 

private-preview/aopt/aopt-workload-details.rst

@@ -22,7 +22,7 @@ Efficiency Analysis
 
 :guilabel:`Efficiency Analysis` is based on the workload's resource efficiency.
 
-* :guilabel:`Confidence level`: Look for the confidence level under the :guilabel:`Efficiency Analysis` label. If the confidence level is something other than high, this probably means that your cluster hasn't sent enough metrics to Splunk IM since you created the workload. In this case, for highly critical business workflows or those that have high variations, wait a few days for the confidence level to increase before you apply the recommendations. :ref:`See details on how this is calculated <aopt-glossary-confidence-level>`.
+* :guilabel:`Confidence level`: Look for the confidence level under the :guilabel:`Efficiency Analysis` label. If the confidence level is something other than high, this probably means that your cluster hasn't sent enough metrics to :new-page:`Splunk Infrastructure Monitoring (IM) <https://docs.splunk.com/observability/en/infrastructure/intro-to-infrastructure.html>` since you created the workload. In this case, for highly critical business workflows or those that have high variations, wait a few days for the confidence level to increase before you apply the recommendations. :ref:`See details on how this is calculated <aopt-glossary-confidence-level>`.
 
 * :guilabel:`Resource Starvation Risk`: This workload's average risk of running out of CPU or memory.
 

private-preview/aopt/aopt-workloads.rst

@@ -23,7 +23,7 @@ The :guilabel:`Application Optimization` dashboard provides a high-level view of
 Workloads
 ==========================================================
 
-* :guilabel:`Total`: The total number of workloads, of all kinds, for which you're sending metrics to Splunk IM. 
+* :guilabel:`Total`: The total number of workloads, of all kinds, for which you're sending metrics to :new-page:`Splunk Infrastructure Monitoring (IM) <https://docs.splunk.com/observability/en/infrastructure/intro-to-infrastructure.html>`. 
 
 * :guilabel:`Processed`: The number of workloads that Application Optimization has processed and that are older than 24 hours. This number doesn't include: 
 
@@ -37,7 +37,7 @@ Workloads
 Workloads by Starvation Risk
 ==========================================================
 
-This is a good tile to check first to see if any of your workloads are at high risk of starvation. Those are the workloads that need immediate attention. You can also find starving workloads by sorting the :guilabel:`Kubernetes Workloads` table by :guilabel:`Starvation Risk`. :ref:`See details on how this risk is calculated <aopt-glossary-starvation-risk>`.
+This is a good tile to check first to see if any of your workloads are at high risk of starvation and need immediate attention. You can also find starving workloads by sorting the :guilabel:`Kubernetes Workloads` table by :guilabel:`Starvation Risk`. :ref:`See details on how this risk is calculated <aopt-glossary-starvation-risk>`.
 
 
 Resource Footprint