Merge pull request #124592 from lindsayt-rt/patch-1

Update deploy-manage-updates-using-updates-view.md

Author: ttorble

articles/update-manager/deploy-manage-updates-using-updates-view.md

@@ -22,7 +22,7 @@ The Updates blade allows you to manage machines from an updates viewpoint. It im
 
 ## Classic use case
 
-This option is helpful when you discover a vulnerability and want to fix it by applying a specific update on all machines on which it was pending. For example, a vulnerability is discovered in software, which can potentially expose the customer's environment to risk like remote code extension. The Central IT team discovers this threat and want to secure their enterprise's environment by applying an update *abc* that would mitigate vulnerability. Using the Updates view, they can apply the update *abc* on all the impacted machines.
+This option is helpful when you discover a vulnerability and want to fix it by applying a specific update on all machines on which it was pending. For example, a vulnerability is discovered in software, which can potentially expose the customer's environment to risk like remote code execution. The Central IT team discovers this threat and want to secure their enterprise's environment by applying an update *abc* that would mitigate vulnerability. Using the Updates view, they can apply the update *abc* on all the impacted machines.
 
  ## Summarized view
 
@@ -68,4 +68,4 @@ You can use either the **Overview** blade or select the **Updates** blade that p
 * [Deploy updates now (on-demand) for single machine](deploy-updates.md)
 * [Schedule recurring updates](scheduled-patching.md)
 * [Manage update settings via Portal](manage-update-settings.md)
-* [Manage multiple machines using update Manager](manage-multiple-machines.md)
+* [Manage multiple machines using update Manager](manage-multiple-machines.md)