doc: avoid using the gender of other people
Using gendered pronouns for an anonymous person applies a gender where none is known and further excludes readers who do not use gendered pronouns. Avoid such examples in the documentation by using "they" or passive voice to avoid the need for a pronoun. Inspired-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Felipe Contreras committed
Jun 15, 2021 at 14:11 UTC
69b3367f6c987b36b98937d8f446f75c5dbc000a
3 files changed
+5
-6
Documentation/SubmittingPatches
+2
-3
@@ -370,9 +370,8 @@ If you like, you can put extra tags at the end:
370
. `Acked-by:` says that the person who is more familiar with the area
371
the patch attempts to modify liked the patch.
372
. `Reviewed-by:`, unlike the other tags, can only be offered by the
373
- reviewer and means that she is completely satisfied that the patch
374
- is ready for application. It is usually offered only after a
375
- detailed review.
373
+ reviewers themselves when they are completely satisfied with the
374
+ patch after a detailed analysis.
375
. `Tested-by:` is used to indicate that the person applied the patch
376
and found it to have the desired effect.
377
Documentation/git-push.txt
+2
-2
@@ -244,8 +244,8 @@ Imagine that you have to rebase what you have already published.
244
You will have to bypass the "must fast-forward" rule in order to
245
replace the history you originally published with the rebased history.
246
If somebody else built on top of your original history while you are
247
-rebasing, the tip of the branch at the remote may advance with her
248
-commit, and blindly pushing with `--force` will lose her work.
247
+rebasing, the tip of the branch at the remote may advance with their
248
+commit, and blindly pushing with `--force` will lose their work.
249
+
250
This option allows you to say that you expect the history you are
251
updating is what you rebased and want to replace. If the remote ref
Documentation/user-manual.txt
+1
-1
@@ -2789,7 +2789,7 @@ A fast-forward looks something like this:
2789
2790
In some cases it is possible that the new head will *not* actually be
2791
a descendant of the old head. For example, the developer may have
2792
-realized she made a serious mistake, and decided to backtrack,
2792
+realized a serious mistake was made and decided to backtrack,
2793
resulting in a situation like:
2794
2795
................................................