fixed syntax

This commit is contained in:
B3H0LD3NK3Y 2021-11-14 07:14:27 -05:00
parent 6d1d040c42
commit e24b901b6c
2 changed files with 6 additions and 6 deletions

View File

@ -6,11 +6,11 @@ Your contributions are always welcome!
- Add one link per Pull Request.
- Add the link: `- [project-name](http://example.com/) - A short description that ends with a period.`
- Keep descriptions concise.
- End descriptions with a period `.`.
- Keep descriptions concise.
- End descriptions with a period `.`.
- Add a section if needed.
- Add the section description.
- Add the section title to Table of Contents.
- Add the section description.
- Add the section title to Table of Contents.
- Search previous suggestions/issues before making a new one, to avoid duplicate suggestions.
- Check your spelling and grammar.
- Remove any trailing whitespace.

View File

@ -91,7 +91,7 @@
## Blog posts and opinions
> Best practices and other ppi on Ansible.
> Best practices and other opinions on Ansible.
- [Ansible (Real Life) Good Practices](https://reinteractive.com/posts/167-ansible-real-life-good-practices) - Best practice guidelines.
- [Testing Ansible Roles Against Windows with Test-Kitchen](https://hodgkins.io/testing-ansible-roles-windows-test-kitchen) - Using Test-Kitchen with Ansible to apply playbooks to Windows machines and test them with [Pester](https://github.com/pester/Pester/).