Fix grammar and spelling (#36)

_posts/2024-11-11-dataverse-solution-version-git-tag.md

@@ -12,7 +12,7 @@ comments: true
 In this guide, we'll set up an Azure DevOps pipeline that automatically tags the latest commit in the main branch with the version number from a Dataverse Solution.xml file. This setup helps track solution versions in Git, making it easy to locate specific versions of your Dataverse solution over time.
 
 
-> **Note:** This tagging process isn't intended for release tags. The tag is moved to the latest commit that matches the version in `Solution.xml`, ensuring that unrelated changes (like config updates) don’t leave the version tag on older commits. However, because this pipeline deletes and recreates tags, it can cause issues if used with release tags or if others rely on specific tags for deployments. For production or release tags, it’s safer to create new versioned tags (like v1.0.1, v1.0.2) for each update rather than overwriting existing tags.
+> **Note:** This tagging process isn't intended for release tags. The tag is moved to the latest commit that matches the version in `Solution.xml`, ensuring that unrelated changes (like config updates) don't leave the version tag on older commits. However, because this pipeline deletes and recreates tags, it can cause issues if used with release tags or if others rely on specific tags for deployments. For production or release tags, it's safer to create new versioned tags, like `v1.0.1` or `release-v1.0.2`, for each update rather than overwriting existing tags.
 
 ## Step 1: Create the Pipeline YAML File
 
@@ -25,7 +25,7 @@ Add the following content to the YAML file:
 
 The PowerShell script in the pipeline does the following:
 
-1. Configures Git with the user’s email and name for tagging.
+1. Configures Git with the user's email and name for tagging.
 2. Checks if `Solution.xml` exists; exits if not found.
 3. Reads the solution name and version from `Solution.xml`.
 4. Combines the solution name and version to create a tag name.
@@ -41,10 +41,10 @@ The PowerShell script in the pipeline does the following:
 5. Select **Exisiting Azure Pipelines YAML file**.
 6. Select the branch and path where you created the YMAL file, then click **Continue**.
 7. Click the dropdown arrow next to **Run** and select **Save**.
-8. To rename the pipeline, click the ... (ellipsis) on the top right, choose **Rename/move pipeline**, and name it `git-tag-solution-version`, then click Save.
+8. To rename the pipeline, click the vertical ellipsis on the top right, choose **Rename/move pipeline**, and name it `git-tag-solution-version`, then click Save.
 
 ## Step 3: Test the Pipeline
 
-1. Make a change to files in the repo. And push your changes.
-2. If you update the solution version you sould see a new tag created with the latest version.![Created Git tag](/assets/img/posts/2024-11-11-dataverse-solution-version-git-tag/commit-history-created-tag.png "Created Git tag"){:class="img-fluid blog-post-img img-thumbnail "}
+1. Make a change to files, commit and push your changes to the remote repository.
+2. If you update the solution version you should see a new tag created with the latest version.![Created Git tag](/assets/img/posts/2024-11-11-dataverse-solution-version-git-tag/commit-history-created-tag.png "Created Git tag"){:class="img-fluid blog-post-img img-thumbnail "}
 3. If you update files other than the solution file verion then you should see the solution git tag move to the latest commit.![Moved Git tag](/assets/img/posts/2024-11-11-dataverse-solution-version-git-tag/commit-history-moved-tag.png "Moved Git tag"){:class="img-fluid blog-post-img img-thumbnail "}