Change the order of items of sample-usecase-template.yml based Issue #…

…287

Based on the discussion results of "What to be done?" is ambiguous - #287, I change the order of item of sample-usecase-template.yml.

   * Summary
   * Why WoT
   * Gaps
   * Description

.github/ISSUE_TEMPLATE/sample-usecase-template.yml

@@ -21,11 +21,11 @@ body:
       value: |
         ## Motivation
   - type: textarea
-    id: what_to_be_done
+    id: Summary
     attributes:
-      label: "What to be done?"
+      label: "Summary"
       description: |
-        Please describe any problems or improvements you would like to make in your use case.
+        Please describe the summary of any problems or improvements you would like to make in your use case.
     validations:
       required: true
   - type: textarea
@@ -36,28 +36,25 @@ body:
         Please describe why you would like to use WoT in your use case.
     validations:
       required: true
-
-  - type: markdown
+  - type: textarea
+    id: gaps
     attributes:
-      value: |
-        ## Use Case Description and Expectations for stakeholders and environments
-
-
+      label: Gaps between the user's need and what's possible today
+      description: |
+        Describe any gaps that are not addressed in the current WoT standards and building blocks
+    validations:
+      required: true
   - type: textarea
     id: description
     attributes:
       label: Description
       description: "Please describe your use case details."
     validations:
       required: true
-  - type: textarea
-    id: gaps
+  - type: markdown
     attributes:
-      label: Gaps between the user's need and what's possible today
-      description: |
-        Describe any gaps that are not addressed in the current WoT standards and building blocks
-    validations:
-      required: true
+      value: |
+        ## Use Case Description and Expectations for stakeholders and environments
   - type: dropdown
     id: targetusers
     attributes: