From owner-svn-doc-head@FreeBSD.ORG Fri Mar 13 06:28:35 2015 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52613C3D; Fri, 13 Mar 2015 06:28:35 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3C4C7F6; Fri, 13 Mar 2015 06:28:35 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t2D6SZff088135; Fri, 13 Mar 2015 06:28:35 GMT (envelope-from brd@FreeBSD.org) Received: (from brd@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t2D6SYUR088131; Fri, 13 Mar 2015 06:28:34 GMT (envelope-from brd@FreeBSD.org) Message-Id: <201503130628.t2D6SYUR088131@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: brd set sender to brd@FreeBSD.org using -f From: Brad Davis Date: Fri, 13 Mar 2015 06:28:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46340 - in head/en_US.ISO8859-1/articles: freebsd-questions ldap-auth linux-emulation pr-guidelines X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 06:28:35 -0000 Author: brd Date: Fri Mar 13 06:28:33 2015 New Revision: 46340 URL: https://svnweb.freebsd.org/changeset/doc/46340 Log: Additional language gender sweep.. Modified: head/en_US.ISO8859-1/articles/freebsd-questions/article.xml head/en_US.ISO8859-1/articles/ldap-auth/article.xml head/en_US.ISO8859-1/articles/linux-emulation/article.xml head/en_US.ISO8859-1/articles/pr-guidelines/article.xml Modified: head/en_US.ISO8859-1/articles/freebsd-questions/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-questions/article.xml Fri Mar 13 03:48:06 2015 (r46339) +++ head/en_US.ISO8859-1/articles/freebsd-questions/article.xml Fri Mar 13 06:28:33 2015 (r46340) @@ -507,15 +507,15 @@ fine, but when I try to reboot the syste Do you have something to contribute beyond what has already been said? In general, Yeah, me too 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 me too answer, you should also include any further relevant information. 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 Modified: head/en_US.ISO8859-1/articles/ldap-auth/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/ldap-auth/article.xml Fri Mar 13 03:48:06 2015 (r46339) +++ head/en_US.ISO8859-1/articles/ldap-auth/article.xml Fri Mar 13 06:28:33 2015 (r46340) @@ -64,7 +64,7 @@ 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 Modified: head/en_US.ISO8859-1/articles/linux-emulation/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/linux-emulation/article.xml Fri Mar 13 03:48:06 2015 (r46339) +++ head/en_US.ISO8859-1/articles/linux-emulation/article.xml Fri Mar 13 06:28:33 2015 (r46340) @@ -657,7 +657,7 @@ 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 Modified: head/en_US.ISO8859-1/articles/pr-guidelines/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/pr-guidelines/article.xml Fri Mar 13 03:48:06 2015 (r46339) +++ head/en_US.ISO8859-1/articles/pr-guidelines/article.xml Fri Mar 13 06:28:33 2015 (r46340) @@ -94,7 +94,7 @@ -STABLE if the problem does not exist in -CURRENT), 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 Needs MFC state.