Merge pull request #16 from gvelasq/patch-1

Author: cderv

README.md

@@ -6,16 +6,16 @@ This repository stores [Github Actions](https://github.com/features/actions) aro
 
 ## Examples
 
-In [Examples](./examples), you will find some YAML workflow file to serve as template to be reuse as base for your project. We are also sharing some links to real examples Github repositories using Quarto with Github Actions for rendering and deploying documents and projects. If you want to add your repository in the list, we welcome a PR.
+In [Examples](./examples), you will find some YAML workflow files to serve as templates to be reused as a base for your project. We are also sharing some links to real example Github repositories using Quarto with Github Actions for rendering and deploying documents and projects. If you want to add your repository in the list, we welcome a PR.
 
 ## Release Management
 
 This repository is using [recommended release management for actions](https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-release-management-for-actions): 
 
 * Github releases with tags are used for updates on the actions. 
 * Semantic versioning is used, with major, minor and possibly patch release. 
-* Major version (such as `v1`) will always point to the last minor or patch release for this major version. (when `v1.0.2` is out, `v1` will point to this update to). This means using `quarto-dev/quarto-actions/install-quarto@v1` in your workflow file will automatically get the updated versions. Using `quarto-dev/quarto-actions/[email protected]` will pinned a specific release.
-* Major version change (`v1` to `v2`) will often come with possible breaking change, and a workflow would require manual update.
+* Major version (such as `v1`) will always point to the last minor or patch release for this major version. (when `v1.0.2` is out, `v1` will point to this update to). This means using `quarto-dev/quarto-actions/install-quarto@v1` in your workflow file will automatically get the updated versions. Using `quarto-dev/quarto-actions/[email protected]` will pin a specific release.
+* Major version change (`v1` to `v2`) will often come with a possible breaking change, and a workflow would require manual update.
 
 Example: