@@ -154,21 +154,21 @@ requirements. If a pull request meets all requirements except the |
154 | 154 |
|
155 | 155 | #### Objections |
156 | 156 |
|
157 | | -**Collaborators can object to a pull request by using the "Request |
158 | | -Changes" GitHub feature**. Dissent comments alone don't constitute an |
159 | | -objection. **Any PR objection must include a clear reason for that objection, |
160 | | -and the objector must remain responsive for further discussion towards |
161 | | -consensus about the direction of the pull request**. Providing a set of |
162 | | -actionable steps alongside the objection is recommended. |
| 157 | +Collaborators can object to a pull request by using the "Request |
| 158 | +Changes" GitHub feature. Dissent comments alone don't constitute an |
| 159 | +objection. Any pull request objection must include a clear reason for that |
| 160 | +objection, and the objector must remain responsive for further discussion |
| 161 | +towards consensus about the direction of the pull request. Where possible, |
| 162 | +provide a set of actionable steps alongside the objection. |
163 | 163 |
|
164 | 164 | If the objection is not clear to others, another collaborator can ask an |
165 | 165 | objecting collaborator to explain their objection or to provide actionable |
166 | | -steps to resolve the objection. **If the objector is unresponsive for seven |
167 | | -days after a collaborator asks for clarification, another collaborator can |
168 | | -dismiss the objection**. |
| 166 | +steps to resolve the objection. If the objector is unresponsive for seven |
| 167 | +days after a collaborator asks for clarification, a collaborator may |
| 168 | +dismiss the objection. |
169 | 169 |
|
170 | | -**Pull requests with outstanding objections must remain open until all |
171 | | -objections are satisfied**. If reaching consensus is not possible, a |
| 170 | +Pull requests with outstanding objections must remain open until all |
| 171 | +objections are satisfied. If reaching consensus is not possible, a |
172 | 172 | collaborator can escalate the issue to the TSC by pinging `@nodejs/tsc` and |
173 | 173 | adding the `tsc-agenda` label to the issue. |
174 | 174 |
|
|