Skip to content

Commit c7d0663

Browse files
authored
Update chaos-studio-private-link-agent-service.md
1 parent 63fc693 commit c7d0663

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/chaos-studio/chaos-studio-private-link-agent-service.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ az rest --verbose --skip-authorization-header --header "Authorization=Bearer $ac
6666
|-|-|-|-|
6767
|subscriptionID|True|String|GUID that represents an Azure subscription ID.|
6868
|resourceGroupName|True|String|String that represents an Azure resource group.|
69-
|CSPAResourceName|True|String|String that represents the name you want to give your Chaos Studio Private Access Resource.|
69+
|CSPAResourceName|True|String|String that represents the name you want to give your Chaos Studio Private Access resource.|
7070
|resourceLocation|True|String|Location where you want the resource to be hosted (must be a support region by Chaos Studio).|
7171

7272
## Create your virtual network, subnet, and private endpoint
@@ -133,7 +133,7 @@ az rest --verbose --skip-authorization-header --header "Authorization=Bearer $ac
133133
```
134134

135135
> [!NOTE]
136-
> The `PrivateAccessID` should exactly match the `resourceID` used to create the CSPA resource in the earlier section **Create a Chaos Studio Private Access resource**.
136+
> The `PrivateAccessID` value should exactly match the `resourceID` value that you used to create the CSPA resource in the earlier section **Create a Chaos Studio Private Access resource**.
137137
138138
## Restart the Azure Chaos Agent service in the VM
139139

@@ -155,4 +155,4 @@ Systemctl restart azure-chaos-agent
155155

156156
## Run your agent-based experiment by using private endpoints
157157

158-
After the restart, Azure Chaos Agent should be able to communicate with the Agent Communication data plane service, and the agent registration to the data plane should be successful. After successful registration, the agent can indicate its status with a heartbeat. Then you can proceed to run the Azure Chaos Agent-based experiments by using private endpoints.
158+
After the restart, Azure Chaos Agent should be able to communicate with the Agent Communication data plane service, and the agent registration to the data plane should be successful. After successful registration, the agent can indicate its status with a heartbeat. Then you can proceed to run the Azure Chaos Agent-based experiments by using private endpoints.

0 commit comments

Comments
 (0)