wording

CONTRIBUTING.md

@@ -84,14 +84,14 @@ If your changes involve the Kanister API types, generate the API documentation u
 ### Commit messages
 
 The basic idea is that we ask all contributors to practice
-[good git commit hygiene](https://www.futurelearn.com/info/blog/telling-stories-with-your-git-history)
+[good git commit hygiene](https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/)
 to make reviews and retrospection easy. Use your git commits to provide context
 for the reviewers, and the folks who will be reading the codebase in the months
 and years to come.
 
 We're trying to keep all commits in `master` to follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
 See [conventions](#commit-conventions) for more info on types and scopes.
-We are using squash and merge approach to PRs which means that commit descriptions are generated from PR descriptions.
+We are using squash and merge approach to PRs which means that commit descriptions are generated from PR titles.
 
 It's recommended to use conventional commits when strarting a PR, but follow-up commits in the PR don't have to follow the convention.