diff --git a/articles/azure-functions/functions-bindings-storage-table.md b/articles/azure-functions/functions-bindings-storage-table.md
index b33b9e482b226..41e2efd712995 100644
--- a/articles/azure-functions/functions-bindings-storage-table.md
+++ b/articles/azure-functions/functions-bindings-storage-table.md
@@ -621,7 +621,7 @@ The Table storage output binding supports the following scenarios:
 
 * **Write one or more rows in C# or C#**
 
-  In C# and C# script, access the output table entity by using a method parameter `ICollector<T> paramName` or `ICollectorAsync<T> paramName`. In C# script, `paramName` is the value specified in the `name` property of *function.json*. `T` specifies the schema of the entities you want to add. Typically, `T` derives from `TableEntity` or implements `ITableEntity`, but it doesn't have to. The partition key and row key values in *function.json* or the `Table` attribute constructor are not used in this scenario.
+  In C# and C# script, access the output table entity by using a method parameter `ICollector<T> paramName` or `IAsyncCollector<T> paramName`. In C# script, `paramName` is the value specified in the `name` property of *function.json*. `T` specifies the schema of the entities you want to add. Typically, `T` derives from `TableEntity` or implements `ITableEntity`, but it doesn't have to. The partition key and row key values in *function.json* or the `Table` attribute constructor are not used in this scenario.
 
   An alternative is to use a `CloudTable paramName` method parameter to write to the table by using the Azure Storage SDK.