Inspired by r231891, use gender neutral pronouns in the places I've

found in LLVM.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@231893 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chandler Carruth 2015-03-11 00:15:44 +00:00
parent dd3224b24f
commit bc026689ab
3 changed files with 5 additions and 5 deletions

View File

@ -58,8 +58,8 @@ Especially it's important to understand chapter 3 of tutorial:
:doc:`tutorial/LangImpl3`
Reader also should know how passes work in LLVM, he could use next article as a
reference and start point here:
Reader also should know how passes work in LLVM, they could use next article as
a reference and start point here:
:doc:`WritingAnLLVMPass`
@ -88,7 +88,7 @@ part describes the merging process.
In every part author also tried to put the contents into the top-down form.
First, the top-level methods will be described, while the terminal ones will be
at the end, in the tail of each part. If reader will see the reference to the
method that wasn't described yet, he will find its description a bit below.
method that wasn't described yet, they will find its description a bit below.
Basics
======

View File

@ -74,7 +74,7 @@
// define it to 0 to indicate otherwise.
//
// If the user's ::std::string and ::string are the same class due to
// aliasing, he should define GTEST_HAS_GLOBAL_STRING to 0.
// aliasing, they should define GTEST_HAS_GLOBAL_STRING to 0.
//
// If the user doesn't define GTEST_HAS_GLOBAL_STRING, it is defined
// heuristically.

View File

@ -503,7 +503,7 @@
# define _TR1_FUNCTIONAL 1
# include <tr1/tuple>
# undef _TR1_FUNCTIONAL // Allows the user to #include
// <tr1/functional> if he chooses to.
// <tr1/functional> if they chooses to.
# else
# include <tr1/tuple> // NOLINT
# endif // !GTEST_HAS_RTTI && GTEST_GCC_VER_ < 40302