per review comments

- Fixed typos, mispellings and slight change of meanings

.github/ISSUE_TEMPLATE/release.md

@@ -8,15 +8,15 @@ assignees: 'kcw-grunt'
 ---
 
 ## Goal 
-The process of publishing/launching a new release of **Litewallet** should be consistent and drama-free.  It should also allow the team to catch errors before they occur. This template should make it easy for any iOS developer in the team to be confident the release meets all our criteria.
+The process of publishing/launching a new release of **Litewallet** should be consistent and drama-free. It should also allow the team to catch errors before they occur. This template should make it easy for any iOS developer in the team to be confident the release meets all our criteria.
 
 ## Prepare code
-- [ ] 1. Locally create a new branch from `develop` with the pattern `release/v#.#.#` (Third dot should always be 0 which is preserved for [PATCHes](https://semver.org))
+- [ ] 1. Locally create a new branch from `develop` with the pattern `release/v#.#.#` (Third dot should always be 0 unless there are bugfixes or [PATCHes](https://semver.org))
 - [ ] 2. Note and write down the changes in the `develop` branch since the last release tag. 
 - [ ] 3. Open a draft release at the [litewallet-ios](https://github.com/litecoin-foundation/litewallet-ios/releases) repo targeting the `main` branch and tag with the pattern: **v#.#.#**
 - [ ] 4. Set the release title (should be the same v#.#.#) in [litewallet-ios](https://github.com/litecoin-foundation/litewallet-ios/releases) and add the release notes...add some flair 🤩🔥😅🍀
 - [ ] 5. Save as Draft **Very important!**
-- [ ] 6. Return the the local branch and do a version bump and build number bump. Commit e.g. : `git commit -m 'version bump'`
+- [ ] 6. Return to the local branch and do a version bump and build number bump. Commit e.g. : `git commit -m 'version bump'`
 - [ ] 7. Publish the release branch e.g. : `git push origin release/v#.#.#`
 - [ ] 8. Review the Pull Request in Github and make sure the CI/CD tests and checks pass.  If there are conflicts they need to be resolved and the version needs to be bumped. Return to step 6
 - [ ] 9. Ask for code reviews and approvals