Unity setup docs

Author: FejZa

docs/01-getting-started/img/vs-marketplace-get-extension.png

@@ -4,7 +4,7 @@ title: Unity Activate License Task
 sidebar_label: Unity Activate License Task
 ---
 
-## About
+# About the Unity Activate License Task
 
 This task is used to activate a Untiy Plus/Pro license on the executing agent machine. You can find the task when editing your pipeline by searching for the name `Unity Activate License`.
 

docs/01-getting-started/img/vs-marketplace-install.png

@@ -4,7 +4,7 @@ title: Unity Build Task
 sidebar_label: Unity Build Task
 ---
 
-## About
+# About the Unity Build Task
 
 This task is responsible for actually building your Unity project and as such the core task of your pipeline. In many cases it will be the only task you'll need from the collection of tasks this extension provides. Unity Build will build your project and provide the output files for further processing as needed. You can find the task when editing your pipeline by searching for the name `Unity Build`.
 

docs/02-tasks/02-unity-setup-task.md

@@ -4,7 +4,7 @@ title: Unity CMD Task
 sidebar_label: Unity CMD Task
 ---
 
-## About
+# About the Unity CMD Task
 
 This task allows for full control over the arguments passed to the Unity command line. It's aimed at advanced users with specific requirements. For most use cases and users the use of the other provided tasks is recommended as it provides a guided and targeted experience. You can find the task when editing your pipeline by searching for the name `Unity CMD`. In short: use this task only if you know what you are doing.
 
@@ -102,18 +102,4 @@ steps:
 
 - script: |
     echo $(unitycmd.logsOutputPath)
-```
-
-### Classic Pipeline Editor
-
-The classic (visual) editor for Azure Pipelines provides input fields for configuring the task. In the simple example below, we set `Unity editors location` to use the default Unity Hub installation path to lookup installed Unity editor versions on the agent running our pipeline. We are also leaving the `Unity project path` field empty, since we know our Unity project is in the repository root. For `Command line arguments` we specify that Unity should target the `standalone` platform and execute our custom build script `MyBuildTools.BuildProject` to perform the build. We are also assigning a `Reference name` to the task, so we can use it to refernce the output variables in the variables list in other tasks of the pipeline. E.g. to get the value of the `logsOutputPath` output variable and insert it into any other input field of a task we can then use `$(unitycmd.logsOutputPath)`.
-
-![Classic Pipeline Designer Task Configuration](../../static/img/unity-cmd-task/unity-cmd-classic.png)
-
----
-
-## Log
-
-When run and successful the task will provide log output similar to this:
-
-![Task Log](../../static/img/unity-cmd-task/unity-cmd-log.png)
+```

docs/02-tasks/03-unity-activate-license-task.md

@@ -2,4 +2,6 @@
 id: unity-create-project-task
 title: Unity Create Project Task
 sidebar_label: Unity Create Project Task
----
+---
+
+# About the Unity Create Project Task

docs/02-tasks/04-unity-build-task.md

@@ -4,7 +4,7 @@ title: Unity Get Project Version Task
 sidebar_label: Unity Get Project Version Task
 ---
 
-## About
+# About the Unity Get Project Version Task
 
 This task will find the Unity Editor version the project was last opened with. This is especially useful
 when you need to perform steps in your pipeline that depend on which Unity version is required for the project to build

docs/02-tasks/05-unity-cmd-task.md

@@ -4,7 +4,7 @@ title: Unity Test Task
 sidebar_label: Unity Test Task
 ---
 
-## About
+# About the Unity Test Task
 
 This task is used for running unit tests in your project. Test results will output into a test results file and the file path is provided for uploading and processing. You can find the task when editing your pipeline by searching for the name `Unity Test`.