Internal change

PiperOrigin-RevId: 293602219
dinhostork · Feb 6, 2020 · 57c895a · 57c895a
1 parent f7f0bb4
commit 57c895a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/review/reviewer/speed.md b/review/reviewer/speed.md
@@ -51,7 +51,7 @@ review.
 
 Instead, wait for a break point in your work before you respond to a request for
 review. This could be when your current coding task is completed, after lunch,
-returning from a meeting, coming back from the microkitchen, etc.
+returning from a meeting, coming back from the breakroom, etc.
 
 ## Fast Responses {#responses}
 

diff --git a/review/reviewer/standard.md b/review/reviewer/standard.md
@@ -104,7 +104,7 @@ the CL, for future readers.)
 
 If that doesn't resolve the situation, the most common way to resolve it would
 be to escalate. Often the
-escalation path is to a broader team discussion, having aTechnical Leadweigh in, asking
+escalation path is to a broader team discussion, having a Technical Lead weigh in, asking
 for a decision from a maintainer of the code, or asking an Eng Manager to help
 out. **Don't let a CL sit around because the author and the reviewer can't come
 to an agreement.**