Additional language gender sweep..
This commit is contained in:
parent
b7a249ca04
commit
0eea1de0eb
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46340
4 changed files with 6 additions and 6 deletions
en_US.ISO8859-1/articles
|
@ -507,15 +507,15 @@ fine, but when I try to reboot the system, I get the message
|
|||
<para>Do you have something to contribute beyond what has already been
|
||||
said? In general, <quote>Yeah, me too</quote> answers do not help
|
||||
much, although there are exceptions, like when somebody is
|
||||
describing a problem he is having, and he does not know whether it is
|
||||
his fault or whether there is something wrong with the hardware or
|
||||
describing a problem they are having, and they do not know whether it is
|
||||
their fault or whether there is something wrong with the hardware or
|
||||
software. If you do send a <quote>me too</quote> answer, you should
|
||||
also include any further relevant information.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Are you sure you understand the question? Very frequently, the
|
||||
person who asks the question is confused or does not express himself
|
||||
person who asks the question is confused or does not express themselves
|
||||
very well. Even with the best understanding of the system, it is
|
||||
easy to send a reply which does not answer the question. This
|
||||
does not help: you will leave the person who submitted the question
|
||||
|
|
|
@ -64,7 +64,7 @@
|
|||
<para>This article is not intended to be an exhaustive account of
|
||||
the security, robustness, or best practice considerations for
|
||||
configuring LDAP or the other services discussed herein. While
|
||||
the author takes care to do everything correctly, he does not
|
||||
the author takes care to do everything correctly, they do not
|
||||
address security issues beyond a general scope. This article
|
||||
should be considered to lay the theoretical groundwork only, and
|
||||
any actual implementation should be accompanied by careful
|
||||
|
|
|
@ -657,7 +657,7 @@
|
|||
<para>Emulation is usually used in a place, where using the original
|
||||
component is not feasible nor possible at all. For example someone
|
||||
might want to use a program developed for a different operating
|
||||
system than he uses. Then emulation comes in handy. Sometimes
|
||||
system than they use. Then emulation comes in handy. Sometimes
|
||||
there is no other way but to use emulation - e.g. when the hardware
|
||||
device you try to use does not exist (yet/anymore) then there is no
|
||||
other way but emulation. This happens often when porting an operating
|
||||
|
|
|
@ -94,7 +94,7 @@
|
|||
<literal>-STABLE</literal> if the problem does not exist in
|
||||
<literal>-CURRENT</literal>), making sure to reference the
|
||||
Problem Report in his commit log (and credit the originator
|
||||
if he submitted all or part of the patch) and, if
|
||||
if they submitted all or part of the patch) and, if
|
||||
appropriate, start an MFC countdown. The bug is set to the
|
||||
<literal>Needs MFC</literal> state.</para>
|
||||
</listitem>
|
||||
|
|
Loading…
Reference in a new issue