fix: change working to remove that merge commits produce unclean git …

…history

rfcs/012-merge-rebase-strategy.md

@@ -56,7 +56,7 @@ Although this seems to work in most cases it's probably a good practice to see i
 ## Solution
 
 [Disable `Create a merge commit` from the GitHub settings](https://docs.github.com/en/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests) 
-as it's probably not suitable for use. Using that option will create merge commits and will prevent a clean Git history. Additionally, suggest also disabling `Rebase and merge` as well although it could be argued to leave it in case someone would like to explicitly include
+to help maintain a linear Git history. Additionally, suggest also disabling `Rebase and merge` as well although it could be argued to leave it in case someone would like to explicitly include
 several commits to the `main` branch. The squash and merge option should work for us in all cases. 
 
 As an alternative or a stricter enforcement of this standard we can also add the [`Require linear history` branch protection rule