From 755f5e085eb241c6b67f9fc163d25ccf6e6b1626 Mon Sep 17 00:00:00 2001 From: Carlo Costino Date: Tue, 13 Feb 2024 16:27:55 -0500 Subject: [PATCH] Update reviewee to author This changeset adjusts the language slightly to use clearer terms for the individuals involved in a code review. --- docs/all.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/all.md b/docs/all.md index afb1ff796..4803102dd 100644 --- a/docs/all.md +++ b/docs/all.md @@ -38,7 +38,7 @@ - [System Description](#system-description) - [Code Reviews](#code-reviews) - [For the reviewer](#for-the-reviewer) - - [For the reviewee](#for-the-reviewee) + - [For the author](#for-the-author) - [Run Book](#run-book) - [Alerts, Notifications, Monitoring](#-alerts-notifications-monitoring) - [Restaging Apps](#-restaging-apps) @@ -771,7 +771,7 @@ community. Given this basis of approaching code reviews, here are some general guidelines and suggestions for how to approach a code review from the perspectives of both -the reviewer and the reviewee. +the reviewer and the author. ### For the reviewer @@ -814,7 +814,7 @@ several concerns about the overall approach, it will likely be helpful to schedule time to speak with the author(s) directly and talk through everything. This can save folks a lot of misunderstanding and back-and-forth! -### For the reviewee +### For the author When receiving a code review, please remember that someone took the time to look over all of your work with a critical eye to make sure our standards are being