Docs: code reviews

[B0berman]

Adding section for code reviews

[jsgalarraga]

There's a lot of good content here. I proposed some format changes.

Overall I also see this documentation with independent paragraphs rather than with a connected narrative, but not sure how to address it 😅

[marwfair]

This is looking great! Just left a couple of small feedback items to improve consistency and readability.

[marwfair]

Keep the words lower case to stay consistent with the other points.

Suggested change

	- Prioritize Clean and Readable Code: Adopting consistent coding styles and best practices helps to ensure that everyone on the team can easily understand and maintain each other's code. It also streamlines onboarding for new team members and enhances collaboration across the board.
	- Prioritize clean and readable code: Adopting consistent coding styles and best practices helps to ensure that everyone on the team can easily understand and maintain each other's code. It also streamlines onboarding for new team members and enhances collaboration across the board.

[marwfair]

Nit: Split this sentence up to make it more readable.

Suggested change

	Writing clear and comprehensive commit messages and adding relevant documentation and comments is particularly helpful when dealing with complex logic, as it gives reviewers additional insight and helps them follow your thought process.
	Writing clear and comprehensive commit messages, along with relevant documentation and comments, is especially valuable when working with complex logic. It provides reviewers with deeper insights and makes it easier for them to understand your thought process.