From owner-svn-doc-all@FreeBSD.ORG  Fri Apr 11 01:25:23 2014
Return-Path: <owner-svn-doc-all@FreeBSD.ORG>
Delivered-To: svn-doc-all@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5F28BEFB;
 Fri, 11 Apr 2014 01:25:23 +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 3E20F1C73;
 Fri, 11 Apr 2014 01:25:23 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
 by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3B1PNLX047593;
 Fri, 11 Apr 2014 01:25:23 GMT (envelope-from wblock@svn.freebsd.org)
Received: (from wblock@localhost)
 by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3B1PNsR047592;
 Fri, 11 Apr 2014 01:25:23 GMT (envelope-from wblock@svn.freebsd.org)
Message-Id: <201404110125.s3B1PNsR047592@svn.freebsd.org>
From: Warren Block <wblock@FreeBSD.org>
Date: Fri, 11 Apr 2014 01:25:23 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r44527 - 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.17
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: <http://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: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>,
 <mailto:svn-doc-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 01:25:23 -0000

Author: wblock
Date: Fri Apr 11 01:25:22 2014
New Revision: 44527
URL: http://svnweb.freebsd.org/changeset/doc/44527

Log:
  Clarity, punctuation, and spelling fixes.

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

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml	Thu Apr 10 22:40:41 2014	(r44526)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml	Fri Apr 11 01:25:22 2014	(r44527)
@@ -131,8 +131,8 @@
 
       <task>If you feel comfortable with large source trees, you can try
 	to build the Git version of Chromium on &os;.  If you are also
-	comfortable with signing Googles Contributor License Agreement,
-	you can join testing and submitting patches upstream.</task>
+	comfortable with signing Google's Contributor License Agreement,
+	you can join in testing and submitting patches upstream.</task>
     </help>
   </project>
 
@@ -195,7 +195,7 @@
       <p>The remaining section is the FAQ.  To help users address the
 	most common problems they might run into with ZFS.  It would be
 	useful to hear experiences, questions, misconceptions, gotchas,
-	stumbling blocks and suggestions for the FAQ section from other
+	stumbling blocks, and suggestions for the FAQ section from other
 	users.  Also, a use cases section that highlights some of the
 	cases where ZFS provides advantages over traditional file
 	systems.</p>
@@ -358,8 +358,8 @@
       <p>Xfce is a free software desktop environment for Unix and
 	Unix-like platforms, such as &os;.  It aims to be fast and
 	lightweight, while still being visually appealing and easy to
-	use.  The Xfce team continues to keep up-to-date each piece of
-	the Xfce Desktop.</p>
+	use.  The Xfce team continues to keep each piece of
+	the Xfce Desktop up to date.</p>
 
       <p>The latest commits concerned:</p>
 
@@ -407,7 +407,7 @@
     <help>
       <task>Add support of DragonFly for xfce4-taskmanger.</task>
 
-      <task>Finish to replace Tango icons theme by GNOME, in order to
+      <task>Finish replacing Tango icon theme with GNOME, in order to
 	close <tt>ports/183690</tt> (see links, it remains
 	Midori).</task>
     </help>
@@ -438,7 +438,7 @@
 	will present multiple Virtual PCI Functions (VF) on the PCI bus.
 	These VFs are fully independent PCI devices that have
 	 access to the resources of the PF.  For example, on a network
-	interface card VFs could transmit and receive packets
+	interface card, VFs could transmit and receive packets
 	independent of the PF.</p>
 
       <p>The most obvious use case for SR-IOV is virtualization.  A
@@ -465,7 +465,7 @@
 
       <p>At present, <tt>ixgbe(4)</tt> is able to create VFs and the
 	<tt>ixgbevf</tt> driver is able to pass traffic.  There is still
-	a fair amount of work to support VLAN tags, multicast addresses
+	a fair amount of work to support VLAN tags, multicast addresses,
 	and other features on the VFs.  Also, the VF configuration needs
 	to be better integrated with the PF initialization path to
 	ensure that resets of the PF do not interrupt operation of the
@@ -633,7 +633,7 @@
 	in libvirt-ready applications without major efforts.</p>
 
       <p>Currently, libvirt supports almost all essential features of
-	bhyve, such as Virtual Machince lifecycle (start, stop), bridged
+	bhyve, such as Virtual Machine lifecycle (start, stop), bridged
 	networking, and virtio/SATA driver support.  The work continues
 	to implement more API calls and to cover more of features
 	offered by bhyve.</p>
@@ -716,9 +716,9 @@
 	default, &os; already uses the ARM EABI on all releases from
 	10.0.</p>
 
-      <p>This is important for users of &os;/arm with an ARMv6 or ARMv7
-	SoC and who use code that makes use of floating-point
-	operations.  It removes the need for the slow software
+      <p>This is important for &os;/arm users running code with
+	floating-point operations on ARMv6 or ARMv7 SoC systems.
+	It removes the need for the slow software
 	floating-point support in <tt>libc</tt>.  This is mostly
 	compatible with the existing ABI, with the exception of how
 	floating-point values are passed into functions.  Because no
@@ -726,8 +726,8 @@
 	<tt>armv6</tt> and <tt>armv6hf</tt> kernels will work with
 	either userland.</p>
 
-      <p>As part of this, some support functions have been updated to
-	use the VFP unit when available.  It is intended the existing
+      <p>As part of this change, some support functions have been updated to
+	use the VFP unit when available.  The existing
 	<tt>armv6</tt> target architecture will be kept for cases where
 	the SoC lacks a VFP unit, or existing binaries that are
 	incompatible with the new ABI.</p>
@@ -758,22 +758,22 @@
     </links>
 
     <body>
-      <p>The current Linux emulation layer relies on using a Linux base
+      <p>The Linux emulation layer relies on a Linux base
 	distribution along with Linux ports of relevant non-base
-	software.  Fedora 10 has been imported in 2006, and it shows
+	software.  Fedora 10 was imported in 2006, and it shows
 	&mdash; current Linux software like Skype 4, Sublime Text 2, or
 	even modern games fail to run with the provided libraries.</p>
 
-      <p>CentOS 6.5 has been released in December 2013 and will be
-	supported until 2017, thus making it an ideal basis for an
+      <p>CentOS 6.5 was released in December 2013 and will be
+	supported until 2017, making it an ideal basis for an
 	update to the ports infrastructure.  Built upon the work of
-	Carlos Jacobo Puga Medina, all ports using Linux has been
+	Carlos Jacobo Puga Medina, all ports using Linux have been
 	updated to work with either Fedora 10 or CentOS 6.5.</p>
 
       <p>The goal of this project is to make CentOS 6.5 the default
 	Linux distribution, so that &os; users can enjoy running modern
-	Linux binaries without having to resort to proper virtualization
-	à la VirtualBox, or even dual-booting.</p>
+	Linux binaries without having to resort to virtualization
+	&agrave; la VirtualBox, or even dual-booting.</p>
     </body>
 
     <sponsor>Goldener Grund OÜ</sponsor>
@@ -991,7 +991,7 @@
 	They have been providing the KDE/&os; team with support for
 	quite a long time and we are very grateful for that.</p>
 
-      <p>A major change has been the depreciation of the KDE3 ports and
+      <p>A major change has been the deprecation of the KDE3 ports and
 	the move of the <tt>KDE4_PREFIX</tt> to <tt>LOCALBASE</tt>.
 	Also, work on Qt5 continues to maturity.  &a.rakuco; has been
 	working with upstream to ensure Baloo (Nepomuk successor in KDE
@@ -1144,7 +1144,7 @@
     </links>
 
     <body>
-      <p>Jenkins is a framework that is used by many companies and open
+      <p>Jenkins is a framework used by many companies and open
 	source projects for Continuous Integration (CI).  CI allows
 	developers to commit code to a Source Code Management (SCM)
 	system such as Subversion, and then have automated programs
@@ -1159,9 +1159,9 @@
 	<tt>jenkins-9.FreeBSD.org</tt> and
 	<tt>jenkins-10.FreeBSD.org</tt>.  He set up software builds of
 	<tt>head</tt> and several <tt>stable</tt> branches on these
-	machines.  The status of these builds is visible via a web
-	interface which is accessible via <tt>jenkins.FreeBSD.org</tt>.
-	When any of these builds fail, emails are sent to
+	machines.  The status of these builds is visible on a web
+	interface accessible at <tt>jenkins.FreeBSD.org</tt>.
+	When any of the builds fail, emails are sent to
 	<tt>freebsd-current</tt> or <tt>freebsd-stable</tt>.  Emails are
 	also sent directly to the list of people who recently committed
 	code to Subversion since the last successful build.</p>
@@ -1175,11 +1175,11 @@
 	randomly crash.  Disabling the <tt>vm.pmap.pcid_enabled</tt>
 	<tt>sysctl(3)</tt> variable seemed to fix the problem.  In
 	<tt>kern/187238</tt>, Henrik Gulbrandsen submitted fixes to the
-	&os; VM to address this problem.  &a.kib; committed these fixes
-	to <tt>head</tt>.  These fixes are being tested now.</p>
+	&os; VM to address this problem.  &a.kib; committed the fixes
+	to <tt>head</tt>, where they are being tested now.</p>
 
-      <p>During the setup of the bhyve VM's which run Jenkins processes,
-	&a.rodrigc; wrote scripts to start bhyve VM's from the
+      <p>During the setup of the bhyve VMs which run Jenkins processes,
+	&a.rodrigc; wrote scripts to start bhyve VMs from the
 	<tt>rc.d</tt> bootup scripts, which were then published at
 	GitHub.</p>
 
@@ -1213,8 +1213,8 @@
 	<li>&a.skreuzer; has experience administering Jenkins systems.
 	  He set up several builds on <tt>jenkins.FreeBSD.org</tt>,
 	  including a Jenkins build of the &os; documentation.  He is
-	  looking into automatic provisioning of VM's running Jenkins in
-	  the &os; cluster using Ansible.</li>
+	  looking into using Ansible for automatic provisioning of VMs running Jenkins in
+	  the &os; cluster.</li>
 
 	<li>&a.rodrigc; will be running a Continuous Testing working
 	  group at the &os; Devsummit in Ottawa on May 15, 2014.
@@ -1248,7 +1248,7 @@
       <task>Set up more Jenkins builds of the &os; ports repository on
 	different &os; versions.</task>
 
-      <task>Integrate with Kyua, so that Jenkins can run Kyua tests, and
+      <task>Integrate with Kyua, so that Jenkins can run Kyua tests and
 	report the results directly in the native Jenkins web UI where
 	test results are reported.</task>
 
@@ -1492,9 +1492,9 @@ device vt_efifb</pre>
 	engine, which can be integrated with cloud orchestration systems
 	like OpenStack or CloudStack.</p>
 
-      <p>This work goal is to enable &os; as a fully supported compute
+      <p>The goal of this work is to make &os; a fully supported compute
 	host for OpenStack using OpenContrail virtualized networking.  The
-	main areas of development are the following:</p>
+	main areas of development are:</p>
 
       <ul>
 	<li>Libvirt hypervisor driver for bhyve.</li>
@@ -1511,7 +1511,7 @@ device vt_efifb</pre>
 	<li>Integration, performance optimization.</li>
       </ul>
 
-      <p>The current state of the development allows for a working demo
+      <p>The current state of development allows for a working demo
 	of OpenStack with compute node component running on a &os;
 	host:</p>
 
@@ -1524,7 +1524,7 @@ device vt_efifb</pre>
 
 	<li>QEMU might also be used instead of bhyve this way.</li>
 
-	<li>The main goal on the networking side is to use OpenContrail
+	<li>The main goal on the networking side is to use the OpenContrail
 	  solution, compliant with the modern OpenStack networking API
 	  ("neutron").</li>
       </ul>
@@ -1621,7 +1621,7 @@ device vt_efifb</pre>
 	<li>Texas Instruments OMAP4</li>
       </ul>
 
-      <p>We do plan to merge this work to <tt>stable/10</tt> in time for
+      <p>We plan to merge this work to <tt>stable/10</tt> in time for
 	10.1-RELEASE.</p>
     </body>
 
@@ -1676,7 +1676,7 @@ device vt_efifb</pre>
 	The second was <tt>auditdistd(8)</tt> improvements for the &os;
 	cluster.</p>
 
-      <p>Work continued on the following Foundation-sponsored projects:
+      <p>Work continued on these Foundation-sponsored projects:
 	Intel graphics driver update by &a.kib;, UEFI boot support for
 	<tt>amd64</tt> by &a.emaste;, autofs automounter and in-kernel
 	iSCSI stack enhancements, bug fixes by &a.trasz;, updated
@@ -1755,7 +1755,7 @@ device vt_efifb</pre>
 
     <body>
       <p>LLDB is the debugger project associated with
-	Clang/LLVM.  It supports the Mac OS X, Linux, and &os; platforms,
+	Clang/LLVM.  It supports Mac OS X, Linux, and &os; platforms,
 	with ongoing work on Windows.  It builds on existing components
 	in the larger LLVM project, for example using Clang's expression
 	parser and LLVM's disassembler.</p>
@@ -1828,7 +1828,7 @@ device vt_efifb</pre>
 
     <body>
       <p>The <tt>auditdistd(8)</tt> daemon is responsible for
-	distributing audit trail files over TCP/IP network securely and
+	distributing audit trail files over TCP/IP networks securely and
 	reliably.</p>
 
       <p>The daemon now supports client-side certificates, which can be
@@ -1871,9 +1871,9 @@ device vt_efifb</pre>
 
     <body>
       <p>SDIO is an interface designed as an extension of the existing
-	SD card standard, to allow connecting different peripherals to
+	SD card standard, allowing connection of different peripherals to
 	the host with the standard SD controller.  Peripherals currently
-	sold at the general market include WLAN/BT modules, cameras,
+	sold on the general market include WLAN/BT modules, cameras,
 	fingerprint readers, and barcode scanners.  The &os; driver is
 	implemented as an extension to the existing MMC bus, adding a
 	lot of new SDIO-specific bus methods.  A prototype of the driver
@@ -1884,7 +1884,7 @@ device vt_efifb</pre>
       <p>SDIO card detection and initialization already work, most
 	needed bus methods are implemented and tested.</p>
 
-      <p>The WiFi driver is able to load a firmware onto the card and
+      <p>The WiFi driver is able to load firmware onto the card and
 	initialize it.  Migration of the MMC stack to the new locking
 	model is necessary in order to work with SDIO cards effectively.
 	The &os; CAM implementation is believed to be a good choice.
@@ -1894,7 +1894,7 @@ device vt_efifb</pre>
 
     <help>
       <task>SDIO stack: finish CAM migration.  The XPT layer is almost
-	ready, what is missing is a SIM module, for which a modified
+	ready.  What is missing is a SIM module, for which a modified
 	version of the SDHCI controller driver will be used, and a
 	peripheral module, where porting the <tt>mmcsd(4)</tt> driver is
 	required.</task>
@@ -1930,7 +1930,7 @@ device vt_efifb</pre>
 	of the GNU Project and can be used with various Unix-like
 	operating systems, including &os;.</p>
 
-      <p>Preperations for merging GNOME&nbsp;3 are moving forward.  The
+      <p>Preparations for merging GNOME&nbsp;3 are moving forward.  The
 	work on the documentation is falling behind a bit, but we got
 	some solid feedback on the rough work to keep this moving
 	forward as well.  In the meantime, deprecation of ports that
@@ -1941,11 +1941,11 @@ device vt_efifb</pre>
       <p>Thanks to a combined effort by Ryan Lortie (GNOME developer),
 	Ting-Wei Lan (upstream contributor), and &a.kwm;, we now have a
 	&os;-powered JHbuild tinderbox.  JHbuild is a build system that
-	lets building GNOME upstream code.  It will attempt twice a day
-	to build gnome components from a specific branch, which is the
-	git master branch most of the time, in order to catch compile
-	issues.  A positive side effect of this is that it lets upstream
-	know GNOME still lives on other systems than Linux.  It also
+	allows building GNOME upstream code.  Twice a day, it will attempt
+	to build Gnome components from a specific branch, usually the
+	git master branch, to catch compile
+	issues.  A positive side effect is that it lets upstream
+	know GNOME still lives on non-Linux systems.  It also
 	exposes the GNOME code base to the Clang compiler and
 	<tt>libc++</tt>.  Since the start of this project over a hundred
 	issues have been fixed.</p>
@@ -1997,8 +1997,8 @@ device vt_efifb</pre>
     <body>
       <p>While the age old version of the GNU Compiler Collection (GCC)
 	in the base system is on its way out with &os;&nbsp;10 and
-	later, there are many users who want (and some platforms which
-	need) to use GCC.</p>
+	later, there are many users who want&mdash;and some platforms which
+	need&mdash;to use GCC.</p>
 
       <p>For that purpose there are various versions of GCC in the ports
 	tree, including <tt>lang/gcc46</tt>, <tt>lang/gcc47</tt>,
@@ -2035,7 +2035,7 @@ device vt_efifb</pre>
   </project>
 
   <project cat='ports'>
-    <title>The Graphics stack on &os;</title>
+    <title>The Graphics Stack on &os;</title>
 
     <contact>
       <person>
@@ -2157,19 +2157,19 @@ device vt_efifb</pre>
 	four new committers, took in three commit bits for safe keeping,
 	and reinstated one commit bit.</p>
 
-      <p>In January, longest serving port manager &a.marcus; stepped
+      <p>In January, the longest serving port manager, &a.marcus;, stepped
 	down from his active duties on the team.  At a similar time
 	&a.itetcu; also stepped down from his duties.  Fortunately, as a
 	result of the first <tt>portmgr-lurkers</tt> intake, we were
 	able to replace them with &a.mat; and &a.antoine;.</p>
 
-      <p>Commencing March 1, the second intake <tt>portmgr-lurkers</tt>
+      <p>Commencing March 1, the second intake of <tt>portmgr-lurkers</tt>
 	started active duty on <tt>portmgr</tt> for a four month duration.
 	The next two candidates are &a.danfe; and &a.culot;.</p>
 
       <p>This quarter also saw the release of the first quarterly
-	branch, namely <tt>2014Q1</tt>.  This branch is intended at
-	providing a stable and high-quality ports tree, with patches
+	branch, namely <tt>2014Q1</tt>.  This branch is intended to
+	provide a stable and high-quality ports tree, with patches
 	related to security fixes as well as packaging and runtime fixes
 	being backported from <tt>head</tt>.</p>
 
@@ -2178,7 +2178,7 @@ device vt_efifb</pre>
     </body>
 
     <help>
-      <task>As previously noted, many PRs continue to languish, we would
+      <task>As previously noted, many PRs continue to languish.  We would
 	like to see committers dedicate themselves to closing as many as
 	possible.</task>
     </help>
@@ -2241,7 +2241,7 @@ device vt_efifb</pre>
 
     <body>
       <p>Not all of the &os; changes to GCC have been reflected upstream.
-	A large amount of the platform support as well as a couple minor
+	A large amount of the platform support as well as a couple of minor
 	improvements like the kernel formatting checker need to be
 	forward ported (and if possible, moved upstream into
 	GCC).</p>
@@ -2271,8 +2271,8 @@ device vt_efifb</pre>
 	possible disruptions of project mail services, such as having
 	troll-, spam- and virus-filters.</p>
 
-      <p>In the first quarter of 2014, the team has implemented the
-	following items that may be interest of the general public:</p>
+      <p>In the first quarter of 2014, the team has implemented these
+	items that may be interest of the general public:</p>
 
       <ul>
 	<li>Continued a discussion on current and possible future mail
@@ -2333,12 +2333,12 @@ device vt_efifb</pre>
 	standards-compliant implementations of the required numerical
 	functions have been added.</p>
 
-      <p>The Core Team has conducted an annual review among the Project
-	teams and hats, where they had to declare if they are wishing to
+      <p>The Core Team conducted an annual review among the Project
+	teams and hats, where team members had to declare whether they wished to
 	continue their service.  As a result, &a.flo; replaced &a.dhw;
 	in the lead role of the Postmaster Team, and &a.gjb; assumed the
 	head Release Engineer position from &a.kensmith;.  The Core Team
-	congratulates to Florian and Glen, and thanks David and Ken for
+	congratulates Florian and Glen, and thanks David and Ken for
 	their long-standing work.</p>
 
       <p>The Core Team approved chartering the Ports Security Team,
@@ -2355,8 +2355,8 @@ device vt_efifb</pre>
 	for <tt>freebsd-update(8)</tt> low.  A related Errata Notice is
 	about to be published soon.</p>
 
-      <p>There was only a single commit bit was taken for safekeeping,
-	we did not have new committers to the <tt>src/</tt> repository in
+      <p>Only a single commit bit was taken for safekeeping.
+	We did not have new committers to the <tt>src/</tt> repository in
 	this quarter.</p>
     </body>
   </project>