[Docs] Update and fix inconsistencies in MsBuild-Sdk, Templates, and additional guides.

Author: Nice3point

docs/Installation.md

@@ -8,7 +8,7 @@ If you don't have it, you can find the latest version here: https://dotnet.micro
 
 The templates are supplied as a Nuget package https://www.nuget.org/packages/Nice3point.Revit.Templates
 
-To install it, open terminal, paste the command and press **Enter**:
+To install it, open the Terminal, paste the command and press **Enter**:
 
 ```shell
 dotnet new install Nice3point.Revit.Templates

docs/Managing-API-compatibility.md

@@ -103,7 +103,7 @@ Example:
 > [!IMPORTANT]  
 > Edit the `.csproj` file only manually, IDEs often break configurations.
 
-Revit MSBuild SDK automatically sets the required `TargetFramework` based on the `RevitVersion`, extracted from the solution configuration name. 
+Revit [MSBuild SDK](https://www.nuget.org/packages/Nice3point.Revit.Sdk) automatically sets the required `TargetFramework` based on the `RevitVersion`, extracted from the solution configuration name. 
 
 If you need to add support for an unreleased or unsupported version of Revit that the SDK doesn't yet know about, you can add a conditional block to specify the `TargetFramework` manually:
 

docs/MsBuild-Sdk.md

@@ -285,11 +285,14 @@ To configure a default debug profile that launches the target Revit version, ena
 </PropertyGroup>
 ```
 
-This sets additional properties (only when values are not already specified):
+If you want to run Revit in a different language or installed in a different directory, also override some properties.:
 
-- `StartAction=Program`
-- `StartProgram=C:\Program Files\Autodesk\Revit $(RevitVersion)\Revit.exe`
-- `StartArguments=/language ENG`
+```xml
+<PropertyGroup>
+    <StartProgram>C:\Program Files\Autodesk\Revit $(RevitVersion)\Revit.exe</StartProgram>
+    <StartArguments>/language ENG</StartArguments>
+</PropertyGroup>
+```
 
 ## Configuration
 

docs/Step‐by‐step-Guide.md

@@ -43,7 +43,7 @@ To create a new project, click **New Solution** in Rider or **Create a new Proje
 
 1. Select the desired [template](Templates.md), such as Revit Addin for a single-project add-in.
 2. Name your project and choose the directory.
-3. Choose additional settings, such as whether to include WPF. If unsure, stick with the default settings.
+3. Choose additional settings, such as whether to include WPF. If unsure, keep the default settings.
 
 ![image](https://github.com/user-attachments/assets/0dbfe226-ad35-4887-9c06-b584a4332dfa)
 
@@ -71,7 +71,7 @@ Debugging is pretty simple, without any additional setup. To debug:
 ## Creating Additional Modules
 
 For larger projects, a single-project solution may not be sufficient. 
-Splitting your plugin into multiple modules is a best practice when managing unrelated processes.
+Splitting your plugin into multiple modules is the best practice when managing unrelated processes.
 
 To add another project to your solution, we will [use](Templates.md) the **Revit AddIn Module** and **Revit AddIn Application** templates.
 
@@ -131,7 +131,7 @@ Follow the steps from previous sections to add projects to this solution:
 Let's customize the build system:
 1. In the **build** project, you will find frequently used configuration files, right now we need **appsettings.json**.
 2. Update the **BundleOptions** section if you plan to publish your application to the Autodesk Store.
-3. The build system automatically finds all projects in the **source** folder, so no additional mapping is required.
+3. If your add-im name differs from the solution name, you will also need to replace the generated by [Sourcy](https://github.com/thomhurst/Sourcy) properties pointing to the project.
 
 ![image](https://github.com/user-attachments/assets/80bc14c9-d10a-4d4a-8360-70f3d5aff242)
 

docs/Templates.md

@@ -66,7 +66,7 @@ Suitable for enterprise development and developers who need a ready-made project
 This template contains:
 
 - `ModularPipelines` build system
-- Installer project, that generates an .msi package
+- Installer project, that generates an **.msi** package
 - Auxiliary files such as `.gitignore`, `Changelog.md` which are usually created in each solution. `Readme.md` contains documentation and instructions for building the project.
 - CI\CD setup
 - JetBrains Rider `Run configurations`
@@ -76,17 +76,17 @@ This template contains:
 
 > [!TIP]  
 > The solution template should be used before the project templates (if you need it).
-And you have to create all plugins in produced solution, in the `source` folder.
+> And you have to create all plugins in the produced solution, in the `source` folder.
 
 ### ModularPipelines
 
-ModularPipelines is used to build a project for various configurations. In this case, for all specified Revit versions. It also allows you to automate other secondary processes, create an
-installer, generate a changelog, etc.
+ModularPipelines is used to build a project for various configurations. In this case, for all specified Revit versions. 
+It also allows you to automate other secondary processes, create an installer, generate a changelog, etc.
 
 More details about ModularPipelines [here](https://github.com/thomhurst/ModularPipelines).
 
 > [!NOTE]  
-> You don't need to use the build system to debug the project, it is only necessary for the publishing release.
+> You don't need to use the build system for the add-ins directly, it's only needs for publishing Releases.
 
 ### Installer