PR suggestions

Author: KJSanchez

assets/dismiss-review.png

@@ -9,6 +9,9 @@ all observations but you should respond to all of them with a informative commen
 the reviewer knows what you did (addressed the changes, have questions about their
 observations, etc.)
 
+It's okay and often faster to use Slack to resolve any disagreement, confusion,
+or ambiguity and then update the thread once consensus is reached. 
+
 If a code change has been made, include a link to the changes so the reviewer
 can find them quickly. First, click on `Files changed` in your PR:
 
@@ -30,9 +33,9 @@ Then, your response can be:
 [fixed](https://github.com/ploomber/jupysql/pull/787/files#diff-15ef0e119ce73b542976f499fcc3cbb967d30af8199e058aec2bc77c30973061R105-R114)
 ```
 
-## **Do not** mark the conversations as resolved
+## **Do not** mark the conversations as resolved or dismiss reviews
 
 The reviewer is responsible for making conversations as resolved.
 
 ![](../assets/resolve-conversation.png)
-
+![](../assets/dismiss-review.png)