[Documentation] Fix typos, broken links and stylings (#2414)

* Fix typos

* Fix broken links

* Fix indentation

Author: David Favretto

docs/_docs/reference/skills/architecture.md

@@ -23,7 +23,7 @@ Within an Enterprise, this could be creating one parent bot bringing together mu
 
 Skills are themselves Bots, invoked remotely and a Skill developer template (.NET, TS) is available to facilitate creation of new Skills.
 
-A key design goal for Skills was to maintain the consistent Activity protocol and ensure the development experience was as close to any normal V4 SDK bot as possible. To that end, a Bot simply starts a `SkilllDialog` which abstracts the skill invocation mechanics.
+A key design goal for Skills was to maintain the consistent Activity protocol and ensure the development experience was as close to any normal V4 SDK bot as possible. To that end, a Bot simply starts a `SkillDialog` which abstracts the skill invocation mechanics.
 
 ## Invocation Flow
 
@@ -32,7 +32,7 @@ A key design goal for Skills was to maintain the consistent Activity protocol an
 ### Dispatcher
 {:.no_toc}
 
-The Dispatcher plays a central role to enabling a Bot to understand how to best process a given utterance. The Dispatch through use of the [Skill CLI]({{site.baseurl}}/reference/botskills) is updated with triggering utterances for a given Skill and a new Dispatch intent is created for a given Skill. An example of a Dispatch model with a point of interest skill having been added is shown below.
+The Dispatcher plays a central role to enabling a Bot to understand how to best process a given utterance. The Dispatch through use of the [Skill CLI]({{site.baseurl}}/reference/skills/botskills) is updated with triggering utterances for a given Skill and a new Dispatch intent is created for a given Skill. An example of a Dispatch model with a point of interest skill having been added is shown below.
 
 ![Dispatch with Skill Example]({{site.baseurl}}/assets/images/skillarchitecturedispatchexample.png)
 

docs/_docs/reference/skills/automotive.md

@@ -63,7 +63,7 @@ An example transcript file demonstrating the Skill in action can be found [here]
 
 ## Language Understanding (LUIS)
 
-LUIS models for the Skill are provided in .LU file format as part of the Skill. These are currently available in English with other languages to follow.
+LUIS models for the Skill are provided in `.lu` file format as part of the Skill. These are currently available in English with other languages to follow.
 
 The following Top Level intents are available with the main `settings` LUIS model
 
@@ -131,36 +131,36 @@ The MSBot tool will outline the deployment plan including location and SKU. Ensu
 
 > After deployment is complete, it's **imperative** that you make a note of the .bot file secret provided as this will be required for later steps. The secret can be found near the top of the execution output and will be in purple text.
 
-- Update your `appsettings.json` file with the newly created .bot file name and .bot file secret.
+- Update your `appsettings.json` file with the newly created `.bot` file name and `.bot` file secret.
 - Run the following command and retrieve the InstrumentationKey for your Application Insights instance and update `InstrumentationKey` in your `appsettings.json` file.
 
 ```
 msbot list --bot YOURBOTFILE.bot --secret YOUR_BOT_SECRET
 ```
 
 ```json
-  {
-    "botFilePath": ".//YOURBOTFILE.bot",
-    "botFileSecret": "YOUR_BOT_SECRET",
-    "ApplicationInsights": {
-      "InstrumentationKey": "YOUR_INSTRUMENTATION_KEY"
-    }
+{
+  "botFilePath": ".//YOURBOTFILE.bot",
+  "botFileSecret": "YOUR_BOT_SECRET",
+  "ApplicationInsights": {
+    "InstrumentationKey": "YOUR_INSTRUMENTATION_KEY"
   }
+}
 ```
 
-- Finally, add the .bot file paths for each of your language configurations (English only at this time).
+- Finally, add the `.bot` file paths for each of your language configurations (English only at this time).
 
 ```json
 "defaultLocale": "en-us",
-  "languageModels": {
-    "en": {
-      "botFilePath": ".//LocaleConfigurations//YOUR_EN_BOT_PATH.bot",
-      "botFileSecret": ""
-    }
-    }
+"languageModels": {
+  "en": {
+    "botFilePath": ".//LocaleConfigurations//YOUR_EN_BOT_PATH.bot",
+    "botFileSecret": ""
+  }
+}
 ```
 
-Once you have followed the deployment instructions above, open the provided .bot file with the Bot Framework Emulator.
+Once you have followed the deployment instructions above, open the provided `.bot` file with the Bot Framework Emulator.
 
 ### Adding the Skill to an existing Virtual Assistant deployment
 
@@ -169,33 +169,33 @@ Follow the instructions below to add the Automotive Skill to an existing Virtual
 1. Update the Virtual Assistant deployment scripts.
     - Add the additional automotive skill LUIS models to the bot.recipe file located within your assistant project: `assistant/DeploymentScripts/en/bot.recipe`
 
-        ```json
-        {
-            "type": "luis",
-            "id": "settings",
-            "name": "settings",
-            "luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings.lu"
-        },
-        {
-            "type": "luis",
-            "id": "settings_name",
-            "name": "settings_name",
-            "luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_name.lu"
-        },
-        {
-            "type": "luis",
-            "id": "settings_value",
-            "name": "settings_value",
-            "luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_value.lu"
-        },
-        ```
-
-    - Add dispatch references to the core LUIS intents for the skill within the **assistant/CognitiveModels/en/dispatch.lu** file as shown below. Only the vehicle settings model is required for dispatch. This enables the Dispatcher to understand your new capabilities and route utterances to your skill
-
-        ```
-        # l_Automotive
-        - [VEHICLE_SETTINGS_CHANGE](../../../../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_dispatch.lu#VEHICLE_SETTINGS_CHANGE)
-        ```
+		```json
+		{
+			"type": "luis",
+			"id": "settings",
+			"name": "settings",
+			"luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings.lu"
+		},
+		{
+			"type": "luis",
+			"id": "settings_name",
+			"name": "settings_name",
+			"luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_name.lu"
+		},
+		{
+			"type": "luis",
+			"id": "settings_value",
+			"name": "settings_value",
+			"luPath": "../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_value.lu"
+		},
+		```
+
+	- Add dispatch references to the core LUIS intents for the skill within the **assistant/CognitiveModels/en/dispatch.lu** file as shown below. Only the vehicle settings model is required for dispatch. This enables the Dispatcher to understand your new capabilities and route utterances to your skill
+    
+		```
+		# l_Automotive
+		- [VEHICLE_SETTINGS_CHANGE](../../../../skills/automotiveskill/automotiveskill/CognitiveModels/LUIS/en/settings_dispatch.lu#VEHICLE_SETTINGS_CHANGE)
+		```
 
 2. Run the following script to deploy the new Automotive Skill LUIS models and to update the dispatcher.