Skip to content

Commit 7d7df70

Browse files
committed
edit pass: status-monitor-v2-articles-batch2
1 parent 7eff9d9 commit 7d7df70

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

articles/azure-monitor/app/status-monitor-v2-api-enable-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ After you enable monitoring, we recommend that you use [Live Metrics](live-strea
3939
> - This cmdlet requires that you review and accept our license and privacy statement.
4040
4141
> [!IMPORTANT]
42-
> This cmdlet requires a PowerShell session with Admin permissions and an elevated execution policy. For more information, see [Run PowerShell as administrator with an elevated execution policy](status-monitor-v2-detailed-instructions.md#run-powershell-as-administrator-with-an-elevated-execution-policy).
42+
> This cmdlet requires a PowerShell session with Admin permissions and an elevated execution policy. For more information, see [Run PowerShell as administrator with an elevated execution policy](status-monitor-v2-detailed-instructions.md#run-powershell-as-admin-with-an-elevated-execution-policy).
4343
4444
## Examples
4545

articles/azure-monitor/app/status-monitor-v2-api-set-config.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This document describes a cmdlet that's a member of the [Az.ApplicationMonitor P
2525
## Description
2626

2727
Sets the config file without repeating a full reinstallation.
28-
You need to restart IIS for the changes to take effect.
28+
Restart IIS for your changes to take effect.
2929

3030
> [!IMPORTANT]
3131
> This cmdlet requires a PowerShell session with Admin permissions.

articles/azure-monitor/app/status-monitor-v2-detailed-instructions.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ These steps will prepare your server to download modules from PowerShell Gallery
122122
- You can confirm this change and audit all PSRepositories by running the `Get-PSRepository` command.
123123

124124
4. Install the newest version of PowerShellGet.
125-
- Description: This module contains the tooling used to get other modules from PowerShell Gallery. Version 1.0.0.1 ships with Windows 10 and Windows Server. Version 1.6.0 or higher is required. To determine which version you have installed, run the `Get-Command -Module PowerShellGet` command.
125+
- Description: This module contains the tooling used to get other modules from PowerShell Gallery. Version 1.0.0.1 ships with Windows 10 and Windows Server. Version 1.6.0 or higher is required. To determine which version is installed, run the `Get-Command -Module PowerShellGet` command.
126126
- Reference: [Installing PowerShellGet](https://docs.microsoft.com/powershell/gallery/installing-psget).
127127
- Command: `Install-Module -Name PowerShellGet`.
128128
- Optional parameters:
@@ -159,7 +159,7 @@ These steps will download the Az.ApplicationMonitor module from PowerShell Galle
159159

160160
If for any reason you can't connect to the PowerShell module, you can manually download and install the Az.ApplicationMonitor module.
161161

162-
### Manually download the latest .nupkg file
162+
### Manually download the latest nupkg file
163163

164164
1. Go to https://www.powershellgallery.com/packages/Az.ApplicationMonitor.
165165
2. Select the latest version in the **Version History** table.
@@ -170,9 +170,9 @@ Install the manually downloaded PowerShell module into a PowerShell directory so
170170
For more information, see [Installing a PowerShell Module](https://docs.microsoft.com/powershell/developer/module/installing-a-powershell-module).
171171

172172

173-
#### Unzip .nupkg as a .zip by using Expand-Archive (v1.0.1.0)
173+
#### Unzip nupkg as a .zip by using Expand-Archive (v1.0.1.0)
174174

175-
- Description: The base version of Microsoft.PowerShell.Archive (v1.0.1.0) can't unzip .nupkg files. Rename the file with the .zip extension.
175+
- Description: The base version of Microsoft.PowerShell.Archive (v1.0.1.0) can't unzip nupkg files. Rename the file with the .zip extension.
176176
- Reference: [Expand-Archive](https://docs.microsoft.com/powershell/module/microsoft.powershell.archive/expand-archive?view=powershell-6).
177177
- Command:
178178

@@ -184,9 +184,9 @@ For more information, see [Installing a PowerShell Module](https://docs.microsof
184184
Expand-Archive -LiteralPath $pathToZip -DestinationPath $pathInstalledModule
185185
```
186186

187-
#### Unzip .nupkg by using Expand-Archive (v1.1.0.0)
187+
#### Unzip nupkg by using Expand-Archive (v1.1.0.0)
188188

189-
- Description: Use a current version of Expand-Archive to unzip .nupkg files without changing the extension.
189+
- Description: Use a current version of Expand-Archive to unzip nupkg files without changing the extension.
190190
- Reference: [Expand-Archive](https://docs.microsoft.com/powershell/module/microsoft.powershell.archive/expand-archive?view=powershell-6) and [Microsoft.PowerShell.Archive](https://www.powershellgallery.com/packages/Microsoft.PowerShell.Archive/1.1.0.0).
191191
- Command:
192192

@@ -196,7 +196,7 @@ For more information, see [Installing a PowerShell Module](https://docs.microsof
196196
Expand-Archive -LiteralPath $pathToNupkg -DestinationPath $pathInstalledModule
197197
```
198198

199-
### Option 2: Unzip and import .nupkg manually
199+
### Option 2: Unzip and import nupkg manually
200200
Install the manually downloaded PowerShell module into a PowerShell directory so it will be discoverable by PowerShell sessions.
201201
For more information, see [Installing a PowerShell Module](https://docs.mircrosoft.com/powershell/developer/module/installing-a-powershell-module).
202202

articles/azure-monitor/app/status-monitor-v2-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,8 +59,8 @@ Each of these options is described in the [detailed instructions](status-monitor
5959

6060
- How do I verify that the enablement succeeded?
6161

62-
There is no cmdlet to verify that enablement succeeded.
63-
We recommend that you use [Live Metrics](https://docs.microsoft.com/azure/azure-monitor/app/live-stream) to quickly determine if your app is sending telemetry.
62+
There's no cmdlet to verify enablement succeeded.
63+
We recommend you use [Live Metrics](https://docs.microsoft.com/azure/azure-monitor/app/live-stream) to quickly determine if your app is sending telemetry.
6464

6565
You can also use [Log Analytics](../log-query/get-started-portal.md) to list all the cloud roles currently sending telemetry:
6666
```Kusto

0 commit comments

Comments
 (0)