@@ -5,14 +5,14 @@ exercises: 0
55---
66::::::::::::::::::::::::::::::::::::::: objectives
77
8- - " Become familiar with what makes a 'good' PR."
8+ - Become familiar with what makes a 'good' PR.
99
1010::::::::::::::::::::::::::::::::::::::::::::::::::
1111
1212:::::::::::::::::::::::::::::::::::::::: questions
1313
14- - " What does it mean to be a 'good' PR?"
15- - " What should you do to make a 'good' PR?"
14+ - What does it mean to be a 'good' PR?
15+ - What should you do to make a 'good' PR?
1616
1717::::::::::::::::::::::::::::::::::::::::::::::::::
1818
@@ -88,8 +88,8 @@ streamline the review process.
8888
8989:::::::::::::::::::::::::::::::::::::::: keypoints
9090
91- - " A pull request should contain _ ONE_ cohesive change."
92- - " A pull request should, ideally, be quickly reviewable."
93- - " A pull request description should give an overview of what, how, and why something changed."
91+ - A pull request should contain _ ONE_ cohesive change.
92+ - A pull request should, ideally, be quickly reviewable.
93+ - A pull request description should give an overview of what, how, and why something changed.
9494
9595::::::::::::::::::::::::::::::::::::::::::::::::::
0 commit comments