edits

Author: diberry

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

@@ -2,7 +2,7 @@
 title: Bindings for Durable Functions - Azure
 description: How to use triggers and bindings for the Durable Functions extension for Azure Functions.
 ms.topic: conceptual
-ms.date: 08/03/2021
+ms.date: 02/08/2022
 ms.author: azfuncdf
 ---
 

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

@@ -3,7 +3,7 @@ title: Function chaining in Durable Functions - Azure
 description: Learn how to run a Durable Functions sample that executes a sequence of functions.
 author: cgillum
 ms.topic: conceptual
-ms.date: 11/29/2019
+ms.date: 02/08/2022
 ms.author: azfuncdf
 ms.devlang: csharp, javascript, python
 ---
@@ -22,7 +22,7 @@ This article explains the following functions in the sample app:
 * `E1_SayHello`: An [activity function](durable-functions-bindings.md#activity-trigger) that prepends a string with "Hello".
 * `HttpStart`: An HTTP triggered [durable client](durable-functions-bindings.md#orchestration-client) function that starts an instance of the orchestrator.
 
-### E1_HelloSequence orchestrator function
+## E1_HelloSequence orchestrator function
 
 # [C#](#tab/csharp)
 
@@ -94,7 +94,7 @@ The `context` object lets you call other *activity* functions and pass input par
 
 ---
 
-### E1_SayHello activity function
+## E1_SayHello activity function
 
 # [C#](#tab/csharp)
 
@@ -148,7 +148,7 @@ Unlike the orchestrator function, an activity function needs no special setup. T
 
 ---
 
-### HttpStart client function
+## HttpStart client function
 
 You can start an instance of orchestrator function using a client function. You will use the `HttpStart` HTTP triggered function to start instances of `E1_HelloSequence`.
 

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

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.topic: reference
 ms.devlang: csharp, javascript
 ms.custom: devx-track-csharp
-ms.date: 02/18/2019
+ms.date: 02/08/2022
 ms.author: cshoe
 ---
 
@@ -48,7 +48,7 @@ To view and edit the contents of *function.json* in the Azure portal, click the
 > [!NOTE]
 > The value of `connection` is the name of an app setting that contains the connection string, not the connection string itself. Bindings use connection strings stored in app settings to enforce the best practice that *function.json* does not contain service secrets.
 
-## C# script example
+# [C# script](#tab/csharp)
 
 Here's C# script code that works with this trigger and binding. Notice that the name of the parameter that provides the queue message content is `order`; this name is required because the `name` property value in *function.json* is `order` 
 
@@ -78,26 +78,7 @@ public class Person
 }
 ```
 
-## JavaScript example
-
-The same *function.json* file can be used with a JavaScript function:
-
-```javascript
-// From an incoming queue message that is a JSON object, add fields and write to Table Storage
-module.exports = async function (context, order) {
-    order.PartitionKey = "Orders";
-    order.RowKey = generateRandomId(); 
-
-    context.bindings.order = order;
-};
-
-function generateRandomId() {
-    return Math.random().toString(36).substring(2, 15) +
-        Math.random().toString(36).substring(2, 15);
-}
-```
-
-## Class library example
+# [C# class library](#tab/csharp-class-library)
 
 In a class library, the same trigger and binding information — queue and table names, storage accounts, function parameters for input and output — is provided by attributes instead of a function.json file. Here's an example:
 
@@ -127,6 +108,29 @@ public class Person
 }
 ```
 
+# [JavaScript](#tab/javascript)
+
+
+
+The same *function.json* file can be used with a JavaScript function:
+
+```javascript
+// From an incoming queue message that is a JSON object, add fields and write to Table Storage
+module.exports = async function (context, order) {
+    order.PartitionKey = "Orders";
+    order.RowKey = generateRandomId(); 
+
+    context.bindings.order = order;
+};
+
+function generateRandomId() {
+    return Math.random().toString(36).substring(2, 15) +
+        Math.random().toString(36).substring(2, 15);
+}
+```
+
+---
+
 You now have a working function that is triggered by an Azure Queue and outputs data to Azure Table storage.
 
 ## Next steps

includes/functions-host-json-durabletask.md

@@ -14,7 +14,9 @@ Configuration settings for [Durable Functions](../articles/azure-functions/durab
 > [!NOTE]
 > All major versions of Durable Functions are supported on all versions of the Azure Functions runtime. However, the schema of the host.json configuration is slightly different depending on the version of the Azure Functions runtime and the Durable Functions extension version you use. The following examples are for use with Azure Functions 2.0 and 3.0. In both examples, if you're using Azure Functions 1.0, the available settings are the same, but the "durableTask" section of the host.json should go in the root of the host.json configuration instead of as a field under "extensions".
 
-### <a name="durable-functions-2-0-host-json"></a>Durable Functions 2.x
+# [Durable Functions 2.x](#tab/2x-durable-functions)
+
+<a name="durable-functions-2-0-host-json"></a>
 
 ```json
 {
@@ -61,10 +63,9 @@ Configuration settings for [Durable Functions](../articles/azure-functions/durab
   }
  }
 }
-
 ```
 
-### Durable Functions 1.x
+# [Durable Functions 1.x](#tab/1x-durable-functions)
 
 ```json
 {
@@ -92,6 +93,7 @@ Configuration settings for [Durable Functions](../articles/azure-functions/durab
   }
 }
 ```
+---
 
 Task hub names must start with a letter and consist of only letters and numbers. If not specified, the default task hub name for a function app is **DurableFunctionsHub**. For  more information, see [Task hubs](../articles/azure-functions/durable/durable-functions-task-hubs.md).