From owner-svn-doc-all@freebsd.org  Wed May 10 03:46:21 2017
Return-Path: <owner-svn-doc-all@freebsd.org>
Delivered-To: svn-doc-all@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96411D65A34;
 Wed, 10 May 2017 03:46:21 +0000 (UTC) (envelope-from bjk@FreeBSD.org)
Received: from repo.freebsd.org (repo.freebsd.org
 [IPv6:2610:1c1:1:6068::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 6D871D5B;
 Wed, 10 May 2017 03:46:21 +0000 (UTC) (envelope-from bjk@FreeBSD.org)
Received: from repo.freebsd.org ([127.0.1.37])
 by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v4A3kKSx017772;
 Wed, 10 May 2017 03:46:20 GMT (envelope-from bjk@FreeBSD.org)
Received: (from bjk@localhost)
 by repo.freebsd.org (8.15.2/8.15.2/Submit) id v4A3kKvP017771;
 Wed, 10 May 2017 03:46:20 GMT (envelope-from bjk@FreeBSD.org)
Message-Id: <201705100346.v4A3kKvP017771@repo.freebsd.org>
X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org
 using -f
From: Benjamin Kaduk <bjk@FreeBSD.org>
Date: Wed, 10 May 2017 03:46:20 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r50246 - head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-all@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "SVN commit messages for the entire doc trees \(except for &quot;
 user&quot; , &quot; projects&quot; , and &quot; translations&quot;
 \)" <svn-doc-all.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-doc-all>,
 <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/>
List-Post: <mailto:svn-doc-all@freebsd.org>
List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-doc-all>,
 <mailto:svn-doc-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2017 03:46:21 -0000

Author: bjk
Date: Wed May 10 03:46:20 2017
New Revision: 50246
URL: https://svnweb.freebsd.org/changeset/doc/50246

Log:
  Run igor (non-whitespace) over the 2017Q1 report

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml	Wed May 10 03:10:17 2017	(r50245)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml	Wed May 10 03:46:20 2017	(r50246)
@@ -135,7 +135,7 @@
   </project>
 
   <project cat='arch'>
-    <title>&os; s390x attempt III</title>
+    <title>&os;/s390x Attempt III</title>
 
     <contact>
       <person>
@@ -158,7 +158,7 @@
 	skeleton (not doing anything yet) using external binutils.</p>
 
       <p>The primary idea of this initial work was to allow for
-	incremental addition of the neccessary architecture-specific code.
+	incremental addition of the necessary architecture-specific code.
 	Having the build framework in place will allow third-party
 	developers to simply type <tt>make</tt>, as they are willing
 	to contribute to the port without having to know &os; build
@@ -181,7 +181,7 @@
   </project>
 
   <project cat='arch'>
-    <title>64-bit PowerPC Book-E support</title>
+    <title>64-bit PowerPC Book-E Support</title>
 
     <contact>
       <person>
@@ -231,7 +231,7 @@
   </project>
 
   <project cat="kern">
-    <title>pNFS server Plan B</title>
+    <title>pNFS Server Plan B</title>
 
     <contact>
       <person>
@@ -249,8 +249,8 @@
 	performed against multiple file servers, with the potential
 	for data access to occur in parallel.  The pNFS
 	&quot;layout&quot; specifies how the division occurs, with
-	metadata operations occuring against the main server, and
-	bulk data operations (read/write/setattr/etc.) occuring via
+	metadata operations occurring against the main server, and
+	bulk data operations (read/write/setattr/etc.) occurring via
 	a layout-specific scheme between the client and data
 	servers.</p>
 
@@ -668,11 +668,11 @@
 	adjusted to behave correctly while sandboxed.  In essence, you only
 	need to patch up the code until it builds.</p>
 
-      <p>Last year we've managed to port a lot of exciting libraries over
+      <p>Last year we have managed to port a lot of exciting libraries over
 	to CloudABI.  Highlights include sandboxing aware versions of
 	<a href="http://www.boost.org/">Boost</a> and
 	<a href="http://leveldb.org/">LevelDB</a>.  Now that these
-	libraries are readily available, we're at the point where we can
+	libraries are readily available, we are at the point where we can
 	shift our focus towards porting full applications.</p>
 
       <p>Late February one of the lead developers of
@@ -899,7 +899,7 @@
 
     <body>
       <p>Final testing and productionization of support for the
-	Marvell Armada38x platform is underway.  The rebase and cleanup
+	Marvell Armada38x platform is under way.  The rebase and cleanup
 	is going well, with patches functioning on top of HEAD and ready for
 	upstreaming.</p>
 
@@ -942,7 +942,7 @@
   </project>
 
   <project cat='proj'>
-    <title>Support for eMMC flash and Faster SD Card Modes</title>
+    <title>Support for eMMC Flash and Faster SD Card Modes</title>
 
     <contact>
       <person>
@@ -1103,7 +1103,7 @@
 	<li>RBD is actually buildable and can be used to manage RADOS BLOCK
 	  DEVICEs.</li>
 
-	<li>Most of the awkward dependancies on Linux-isms are deleted
+	<li>Most of the awkward dependencies on Linux-isms are deleted
 	  &mdash; only <tt>/bin/bash</tt> is here to stay.</li>
       </ul>
 
@@ -1259,7 +1259,7 @@
       <p>Core is looking for new volunteers to help out with several of
 	the teams that manage various aspects of the project.  In
 	particular, Postmaster and the Security Team are in need of new blood.
-	Recruiting for a new member of the Security Team is well underway, but anyone
+	Recruiting for a new member of the Security Team is well under way, but anyone
 	interested in joining any of the teams is encouraged to make
 	themselves known either to Core, or directly to the teams
 	concerned.</p>