From 0b772ca50af5d5ede913eac684b0add0846319e4 Mon Sep 17 00:00:00 2001
From: "J. Ryan Stinnett" <jryans@gmail.com>
Date: Fri, 13 Mar 2020 16:48:03 +0000
Subject: [PATCH] Tweak issue assigning

Co-Authored-By: Travis Ralston <travpc@gmail.com>
---
 docs/review.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/review.md b/docs/review.md
index ebe79588f6..ae67fa5294 100644
--- a/docs/review.md
+++ b/docs/review.md
@@ -43,8 +43,7 @@ When reviewing code, here are some things we look for and also things we avoid:
 * Avoid force pushing to a PR after first round of review
 * Use merge commits when landing
 * PR author merges after review (assuming they have write access)
-* Assign issues only when in progress (don’t overly assign things so it’s clear
-  that anyone on the team can pick up)
+* Assign issues only when in progress to indicate to others what can be picked up
 
 ## Design and Product Review