User Story
AS a Orcasound dev contributer I WANT to know exactly what the procedure is for code reviewing pull requests in the Orcahome repository SO THAT I don't merge bad code into the main branch.

Description
The intent of this story is to add rules to code reviewing and merging new code to main so that it doesn't rely on one Lead Dev to review and merge all pull requests. The new rules should include...

1. Pull requests require 2 code reviews before they can be merged
2. Any contributing developer can perform code reviews
3. Any pull request with 2 code reviews can be merged to main
4. Need branching rules in place in order to protect the main production branch (@paulcretu suggested a branching process to Scott Viers, and we would like some specifics)

Acceptance Criteria
GIVEN that I am looking at the orcahome repository WHEN I look at the main page THEN I can see the process for branching from main/ conducting and requesting code reviews under the "Deploy on Vercel" section of the front page READMe (as specified in the above description)