Skip to content

Commit 37772e8

Browse files
Apply suggestions from code review
Co-authored-by: Safia Abdalla <[email protected]>
1 parent 55b45d3 commit 37772e8

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/database/azure-cosmos-db-integration.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ For more information on keyed services, see [.NET dependency injection: Keyed se
9393

9494
<!-- TODO: Add xref to AddAzureCosmosDatabase when available -->
9595

96-
In the app host, the database resource can be added as a child resource to the parent <xref:Aspire.Hosting.AzureCosmosDBResource>. In your client-consuming project, you can deep-link to the database resource by name, registering a <xref:Microsoft.Azure.Cosmos.Database> instance for use with dependency injection. For example, consider the following code that calls `AddAzureCosmosDatabase` on an <xref:Microsoft.Extensions.Hosting.IHostApplicationBuilder> instance:
96+
In the app host, the database resource (<xref:Aspire.Hosting.AzureCosmosDBDatabaseResource>) can be added as a child resource to the parent <xref:Aspire.Hosting.AzureCosmosDBResource>. In your client-consuming project, you can deep-link to the database resource by name, registering a <xref:Microsoft.Azure.Cosmos.Database> instance for use with dependency injection. For example, consider the following code that calls `AddAzureCosmosDatabase` on an <xref:Microsoft.Extensions.Hosting.IHostApplicationBuilder> instance:
9797

9898
```csharp
9999
builder.AddAzureCosmosDatabase(connectionName: "customers");
@@ -148,7 +148,7 @@ The preceding example code demonstrates how to register two databases, `details`
148148

149149
<!-- TODO: Add xref to AddAzureCosmosContainer when available -->
150150

151-
When you add a Cosmos DB resource in the app host project, you can also add an Azure Cosmos DB container resource as well. The container resource is considered a child resource to the parent <xref:Aspire.Hosting.AzureCosmosDBResource>. In your client-consuming project, you can deep-link to the container resource by name, registering a <xref:Microsoft.Azure.Cosmos.Container> instance for use with dependency injection. For example, consider the following code that calls `AddAzureCosmosContainer` on an <xref:Microsoft.Extensions.Hosting.IHostApplicationBuilder> instance:
151+
When you add a Cosmos DB resource in the app host project, you can also add an Azure Cosmos DB container resource as well. The container resource is considered a child resource to the parent <xref:Aspire.Hosting.AzureCosmosDBDatabaseResource>. In your client-consuming project, you can deep-link to the container resource by name, registering a <xref:Microsoft.Azure.Cosmos.Container> instance for use with dependency injection. For example, consider the following code that calls `AddAzureCosmosContainer` on an <xref:Microsoft.Extensions.Hosting.IHostApplicationBuilder> instance:
152152

153153
```csharp
154154
builder.AddAzureCosmosContainer(connectionName: "details");

docs/messaging/azure-web-pubsub-integration.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ public class ExampleService(
258258
}
259259
```
260260

261-
If you want to register a single `WebPubSubServiceClient` instance with a specific connection name, there's an overload that uses the connection name as the service key. Call the `AddAzureWebPubSubServiceClient` method. This method registers the client as a singleton service in the dependency injection container.
261+
If you want to register a single `WebPubSubServiceClient` instance with a specific connection name, there's an overload that uses the connection name as the service key. Call the `AddKeyedAzureWebPubSubServiceClient` method. This method registers the client as a singleton service in the dependency injection container.
262262

263263
```csharp
264264
builder.AddKeyedAzureWebPubSubServiceClient(connectionName: "web-pubsub");

0 commit comments

Comments
 (0)