Swapped the layout

Extensions/XplatGenerateReleaseNotes/V2/task.json

@@ -22,6 +22,11 @@
       "name": "advanced",
       "displayName": "Advanced",
       "isExpanded": false
+    },
+    {
+      "name": "handlebars",
+      "displayName": "Handlebars",
+      "isExpanded": false
     },
      {
       "name": "outputs",
@@ -162,7 +167,7 @@
       "defaultValue": "",
       "required": false,
       "helpMarkDown": "A custom Handlebars extension written as a JavaScript module e.g. module.exports = {foo: function () {return 'Returns foo';}};",
-      "groupName":"advanced"
+      "groupName":"handlebars"
      }
 
    ],

Extensions/XplatGenerateReleaseNotes/readme.md

@@ -203,7 +203,7 @@ The task takes the following parameters
 * (Advanced V2 only) anyFieldContent symbol to represent any value when match field in the WI Loop, defaults to equals '*'
 * (Advanced V2 only) Do not generate release notes of a re-deploy. If this is set, and a re-deploy occurs the task will succeeds with a warning
 * (Advanced V2 only) Primary Only. If this is set only WI and CS associated with primary artifact are listed, default is false so all artifacts scanned.
-* (Advanced V2 only) customHandlebarsExtensionCode. A custom Handlebars extension written as a JavaScript module e.g. module.exports = {foo: function () {return 'Returns foo';}};
+* (Handlebars V2 only) customHandlebarsExtensionCode. A custom Handlebars extension written as a JavaScript module e.g. module.exports = {foo: function () {return 'Returns foo';}};
 * (Outputs) Optional: Name of the variable that release notes contents will be copied into for use in other tasks. As an output variable equates to an environment variable, so there is a limit on the maximum size. For larger release notes it is best to save the file locally as opposed to using an output variable.
 
 ## Output location ##