Merge pull request #272088 from nikhilkaul-msft/new-year-updates

New year updates

Author: prmerger-automator[bot]

articles/chaos-studio/chaos-studio-fault-library.md

@@ -53,7 +53,7 @@ The faults listed in this article are currently available for use. To understand
 | | **Windows**: None. |
 | Urn | urn:csci:microsoft:agent:cpuPressure/1.0 |
 | Parameters (key, value)  | |
-| pressureLevel | An integer between 1 and 99 that indicates how much CPU pressure (%) is applied to the VM. |
+| pressureLevel | An integer between 1 and 99 that indicates how much CPU pressure (%) is applied to the VM in terms of **% CPU Usage** |
 | virtualMachineScaleSetInstances | An array of instance IDs when you apply this fault to a virtual machine scale set. Required for virtual machine scale sets in uniform orchestration mode. [Learn more about instance IDs](../virtual-machine-scale-sets/virtual-machine-scale-sets-instance-ids.md#scale-set-instance-id-for-uniform-orchestration-mode). |
 
 ### Sample JSON

articles/chaos-studio/chaos-studio-tutorial-agent-based-cli.md

@@ -13,7 +13,7 @@ ms.devlang: azurecli
 
 # Create a chaos experiment that uses an agent-based fault with the Azure CLI
 
-You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you cause a high CPU event on a Linux virtual machine (VM) by using a chaos experiment and Azure Chaos Studio. Run this experiment to help you defend against an application from becoming resource starved.
+You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you cause a high % of CPU utilization event on a Linux virtual machine (VM) by using a chaos experiment and Azure Chaos Studio. Run this experiment to help you defend against an application from becoming resource starved.
 
 You can use these same steps to set up and run an experiment for any agent-based fault. An *agent-based* fault requires setup and installation of the chaos agent. A service-direct fault runs directly against an Azure resource without any need for instrumentation.
 

articles/chaos-studio/chaos-studio-tutorial-agent-based-portal.md

@@ -12,7 +12,7 @@ ms.custom: template-how-to
 
 # Create a chaos experiment that uses an agent-based fault with the Azure portal
 
-You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you cause a high CPU event on a Linux virtual machine (VM) by using a chaos experiment and Azure Chaos Studio. Running this experiment can help you defend against an application from becoming resource starved.
+You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you cause a high % of CPU utilization event on a Linux virtual machine (VM) by using a chaos experiment and Azure Chaos Studio. Running this experiment can help you defend against an application from becoming resource starved.
 
 You can use these same steps to set up and run an experiment for any agent-based fault. An *agent-based* fault requires setup and installation of the chaos agent. A service-direct fault runs directly against an Azure resource without any need for instrumentation.
 
@@ -67,7 +67,7 @@ Now you can create your experiment. A chaos experiment defines the actions you w
 1. You're now in the Chaos Studio experiment designer. You can build your experiment by adding steps, branches, and faults. Give a friendly name to your **Step** and **Branch**. Then select **Add action > Add fault**.
 
    ![Screenshot that shows the experiment designer.](images/tutorial-agent-based-add-designer.png)
-1. Select **CPU Pressure** from the dropdown list. Fill in **Duration** with the number of minutes to apply pressure. Fill in **pressureLevel** with the amount of CPU pressure to apply. Leave **virtualMachineScaleSetInstances** blank. Select **Next: Target resources**.
+1. Select **CPU Pressure** from the dropdown list. Fill in **Duration** with the number of minutes to apply pressure. Fill in **pressureLevel** with the % of CPU utilization pressure that you want to apply. Leave **virtualMachineScaleSetInstances** blank. Select **Next: Target resources**.
 
    ![Screenshot that shows fault properties.](images/tutorial-agent-based-add-fault.png)
 1. Select your VM and select **Next**.