Merge pull request #99069 from cgillum/patch-11

Fix typo in signalEntity client sample function

Author: PRMerger8

articles/azure-functions/durable/durable-functions-bindings.md

@@ -514,7 +514,7 @@ If you're using scripting languages (for example, *.csx* or *.js* files) for dev
     "taskHub": "<Optional - name of the task hub>",
     "connectionName": "<Optional - name of the connection string app setting>",
     "type": "durableClient",
-    "direction": "out"
+    "direction": "in"
 }
 ```
 

articles/azure-functions/durable/durable-functions-entities.md

@@ -161,7 +161,7 @@ The following examples illustrate these various ways of accessing entities.
 
 ### Example: Client signals an entity
 
-To access entities from an ordinary Azure Function, which is also known as a client function, use the [entity client output binding](durable-functions-bindings.md#entity-client). The following example shows a queue-triggered function signaling an entity using this binding.
+To access entities from an ordinary Azure Function, which is also known as a client function, use the [entity client binding](durable-functions-bindings.md#entity-client). The following example shows a queue-triggered function signaling an entity using this binding.
 
 ```csharp
 [FunctionName("AddFromQueue")]
@@ -182,7 +182,7 @@ const df = require("durable-functions");
 module.exports = async function (context) {
     const client = df.getClient(context);
     const entityId = new df.EntityId("Counter", "myCounter");
-    await context.df.signalEntity(entityId, "add", 1);
+    await client.signalEntity(entityId, "add", 1);
 };
 ```