Plural pronouns for singular annoys me.
I really believe in gender fairness and fluidness in prounouning, and I get why "they" is always better to use, and that the "one's request" construction is too tortured. So, I tend to just write everything in plurals if possible which keeps 'they' but makes the number grammatically agree. Yes, I know that the ADT made "they/them used as singular" as 2015 word of the year. (see https://en.wikipedia.org/wiki/Word_of_the_year#American_Dialect_Society so maybe some nun slapped the table too hard with her ruler when made some plural/singular mistake with a pronoun when I was in grade school, but I have a compulsive need to change everything to plural when I see "they" and am editing a document. ;)
This commit is contained in:
parent
6e91d81ce1
commit
3f2f76019b
1 changed files with 3 additions and 3 deletions
|
@ -56,7 +56,7 @@ following conditions:
|
||||||
|
|
||||||
Using these same conditions, the administrator can define questions that are
|
Using these same conditions, the administrator can define questions that are
|
||||||
conditional on other questions' answers. These questions are only presented
|
conditional on other questions' answers. These questions are only presented
|
||||||
to the requestor when they submit an answer that meets the specified conditions.
|
to the requestors when they submit an answer that meets the specified conditions.
|
||||||
For illustration purposes, the common deployment is expected to have
|
For illustration purposes, the common deployment is expected to have
|
||||||
relatively few unconditional questions about each expense (type of expense,
|
relatively few unconditional questions about each expense (type of expense,
|
||||||
receipt, amount), and then a series of conditional questions based on those
|
receipt, amount), and then a series of conditional questions based on those
|
||||||
|
@ -65,7 +65,7 @@ accommodations expenses, etc.).
|
||||||
|
|
||||||
### Requestor workflow
|
### Requestor workflow
|
||||||
|
|
||||||
Requestor can log in and see the status of all their requests. They can also
|
Requestors can log in and see the status of all their requests. They can also
|
||||||
create a new request, which starts either the Pre-Approval or the In Progress
|
create a new request, which starts either the Pre-Approval or the In Progress
|
||||||
state.
|
state.
|
||||||
|
|
||||||
|
@ -98,7 +98,7 @@ Submitted state.
|
||||||
|
|
||||||
Bookkeepers can log into the system and see all requests.
|
Bookkeepers can log into the system and see all requests.
|
||||||
|
|
||||||
When a bookkeeper reviews a Submitted report, they can change the report's
|
When bookkeepers reviews a Submitted report, they can change the report's
|
||||||
state, and include a note explaining why the report was moved to that state
|
state, and include a note explaining why the report was moved to that state
|
||||||
(e.g., moved back to In Progress because a specific receipt was insufficient
|
(e.g., moved back to In Progress because a specific receipt was insufficient
|
||||||
documentation). When they do this, the system sends e-mail to the requestor
|
documentation). When they do this, the system sends e-mail to the requestor
|
||||||
|
|
Loading…
Reference in a new issue