Skip to content

Commit e03a57d

Browse files
committed
Fix type in the README
1 parent c8076ee commit e03a57d

File tree

1 file changed

+2
-2
lines changed
  • sdk/resourcemanager/Azure.ResourceManager

1 file changed

+2
-2
lines changed

sdk/resourcemanager/Azure.ResourceManager/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -145,10 +145,10 @@ Console.WriteLine($"Vnet: {id.Parent.Name}");
145145
Console.WriteLine($"Subnet: {id.Name}");
146146
```
147147

148-
## Managing Existing Resources by Resouce Identifier
148+
## Managing Existing Resources by Resource Identifier
149149
Performing operations on resources that already exist is a common use case when using the management client libraries. In this scenario, you usually have the identifier of the resource you want to work on as a string. Although the new object hierarchy is great for provisioning, and working within the scope of a given parent, it isn't the most efficient when it comes to this specific scenario.
150150

151-
Here's an example how you can access an `AvailabilitySet` object and manage it directly with its id:
151+
Here's an example how you can access an `AvailabilitySet` object and manage it directly with its ID:
152152
```C# Snippet:Readme_ManageAvailabilitySetOld
153153
ResourceIdentifier id = new ResourceIdentifier("/subscriptions/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/resourceGroups/workshop2021-rg/providers/Microsoft.Compute/availabilitySets/ws2021availSet");
154154
// We construct a new client to work with

0 commit comments

Comments
 (0)