diff --git a/docs/storage/azure-storage-queues-component.md b/docs/storage/azure-storage-queues-component.md
index 3ab4018033..7b6ea54229 100644
--- a/docs/storage/azure-storage-queues-component.md
+++ b/docs/storage/azure-storage-queues-component.md
@@ -134,11 +134,11 @@ builder.AddAzureQueueService(
 In your orchestrator project, add a Storage Queue connection and consume the connection using the following methods, such as <xref:Aspire.Hosting.AzureResourceExtensions.AddAzureStorage%2A>:
 
 ```csharp
-var queue = builder.AddAzureStorage("storage")
-    .AddQueues("queue");
+var queues = builder.AddAzureStorage("storage")
+    .AddQueues("queues");
 
 var exampleProject = builder.AddProject<Projects.ExampleProject>()
-    .WithReference(queue);
+    .WithReference(queues);
 ```
 
 The <xref:Aspire.Hosting.AzureResourceExtensions.AddQueues%2A> method will read connection information from the AppHost's configuration (for example, from "user secrets") under the `ConnectionStrings:queue` config key. The <xref:Aspire.Hosting.ResourceBuilderExtensions.WithReference%2A> method passes that connection information into a connection string named queue in the `ExampleProject` project. In the _Program.cs_ file of `ExampleProject`, the connection can be consumed using:
diff --git a/docs/storage/azure-storage-tables-component.md b/docs/storage/azure-storage-tables-component.md
index 7b7ca137e4..3184713a67 100644
--- a/docs/storage/azure-storage-tables-component.md
+++ b/docs/storage/azure-storage-tables-component.md
@@ -151,11 +151,12 @@ In your orchestrator project, register the Azure Table Storage component and con
 
 ```csharp
 // Service registration 
-var tableStorage = builder.AddAzureTableService("tables");
+var tables = builder.AddAzureStorage("storage")
+    .AddTables("tables");
 
 // Service consumption 
 Builder.AddProject<MyApp.ExampleProject>() 
-    .WithReference(tableStorage)
+    .WithReference(tables)
 ```
 
 For more information, see <xref:Aspire.Hosting.ResourceBuilderExtensions.WithReference%2A>.