Minor tweaks for README.

Author: mzodelegatedk

README.md

@@ -8,7 +8,7 @@
   </a>
 </p>
 
-# 👋 Introductions
+# 👋 Introduction
 
 <p className="text-gray-700 mb-4">
   <strong>Data Model Viewer</strong> is your centralized tool for exploring and understanding your Dataverse metadata. Designed with clarity and efficiency in mind, it gives you a single, streamlined access point to view and navigate your data tables.
@@ -85,7 +85,7 @@ The pipeline expects a variable group called `DataModel`. It must have the follo
 * AzureLocation: Name of the location for the resource group in Azure (e.g. "westeurope" - not the display name which is "West Europe").
 * AzureResourceGroupName: Name of the Resource Group in Azure. If this matches an existing group in the location above that will be used for the DMV resources, if not a new resource group will be created.
 * DataverseUrl: URL for the Dataverse environment which the data model will be based on (e.g. "https://mySystem-dev.crm4.dynamics.com/".
-* DataverseSolutionNames: Comma-seperated list of solutions to based DMV on.
+* DataverseSolutionNames: Comma-seperated list of solutions to based DMV on. Use the logical names (not display names).
 * WebsiteName: Used for the url of the web app presenting the data model to the user. The full URL will be in the format "https://wa-{WebsiteName}.azurewebsites.net/" and must be globally unique. 
 * WebsitePassword: Password used by DMV users to login to the generated site.
 * WebsiteSessionSecret: Key to encrypt the session token with (You can set it to whatever you like, but recommended 32 random characters).
@@ -111,17 +111,17 @@ The `azure-pipelines-external.yml` file is a reusable Azure DevOps pipeline temp
    - `azure-pipelines-external.yml`
 
 2. **Set Up Variables and Service Connection**  
-   - Create a variable group (e.g., `DataModel`) in your Azure DevOps project with all required variables (see the "Setting in pipeline" section above for details).
+   - Create a variable group (e.g. called `DataModel`) in your Azure DevOps project with all required variables (see the "Setting in pipeline" section above for details).
    - Ensure you have an Azure Resource Manager service connection configured (the name should match the one set in the earlier configured variable `AzureServiceConnectionName`).
 
 3. **Configure the Pipeline**  
-   - Add a new pipeline in Azure DevOps using the `azure-pipelines-external.yml` file as the pipeline definition.
-   - Adjust the parameters in the YAML file as needed for your environment (e.g., variable group name, resource group, location).
+   - Add a new "Azure Repos Git" pipeline in Azure DevOps and choose the `azure-pipelines-external.yml` file from your repository as the "Existing Azure Pipelines YAML file" to base the pipeline on.
+   - Adjust the parameters in the YAML file as needed for your environment (usually only if you chose another name for the variable group than "Datamodel").
 
 4. **Pipeline Execution**  
    - The first time the pipeline is run you will see a "This pipeline needs permission to access a resource..." click "View" and give it permission to access the variable group you have created.
    - The pipeline will clone the public DataModelViewer repository, build the application, and deploy it using the shared templates.
-   - The pipeline is scheduled to run daily at 03:00 AM by default. You can adjust or remove the schedule as needed.
+   - The pipeline is scheduled to run daily at 03:00 AM by default. You can adjust or remove the schedule as needed. You can of course also run the pipeline ad-hoc if you wish.
 
 ## Notes