svn commit: r43644 - head/en_US.ISO8859-1/htdocs/news/status

Warren Block wblock at FreeBSD.org
Sun Jan 26 00:10:46 UTC 2014


Author: wblock
Date: Sun Jan 26 00:10:46 2014
New Revision: 43644
URL: http://svnweb.freebsd.org/changeset/doc/43644

Log:
  Minor punctuation and spelling fixes, add ASCII cat pictures.

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml	Sat Jan 25 20:00:48 2014	(r43643)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml	Sun Jan 26 00:10:46 2014	(r43644)
@@ -18,7 +18,7 @@
     <p>The last quarter of 2013 was very active for the &os;
       community, much like the preceding quarters.  Many advances were
       made in getting &os; to run on ARM-based System-on-Chip boards
-      like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6 and
+      like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6, and
       Vybrid VF6xx.  &os; is also becoming a better platform for Xen
       and the Amazon Elastic Compute Cloud.  There are plans for &os;
       to become a fully supported compute host for OpenStack.  The I/O
@@ -434,8 +434,8 @@
     <body>
       <p>The i.MX range is a family of Freescale Semiconductor
 	proprietary microprocessors for multimedia applications based on
-	the ARM architecture and focused on low-power consumption.  The
-	i.MX6x series is based on the ARM Cortex A9 solo, dual or quad
+	the ARM architecture and focused on low power consumption.  The
+	i.MX6x series is based on the ARM Cortex A9 solo, dual, or quad
 	cores.  Initial support for them has been committed to
 	<tt>head</tt>, and merged to <tt>stable/10</tt>.  All members of
 	the i.MX6 family (Solo, Dual, and Quad core) are supported, but
@@ -620,7 +620,7 @@
 	of context switches.</p>
 
       <p>Thanks to these <tt>cam(4)</tt> and <tt>geom(4)</tt> changes,
-	the peak I/O rate has doubled on comptemporary hardware, reaching
+	the peak I/O rate has doubled on contemporary hardware, reaching
 	up to 1,000,000 IOPS!</p>
     </body>
 
@@ -710,9 +710,9 @@
 
       <p>The <tt>devel/py-distribute</tt> port has been replaced by the
 	refreshed <tt>devel/py-setuptools</tt> port, which comes with a
-	lot of features that simplify the ways of installing Python
+	lot of features that simplify the methods of installing Python
 	packages.  The change also led us to install everything through
-	Setuptools now, which resembles a PyIP a bit and allows us to
+	Setuptools now, which resembles PyIP a bit and allows us to
 	perform some major cleanup on the distutils installation
 	behaviour.</p>
 
@@ -975,8 +975,8 @@
 	Ports Collection, thanks to the efforts of Jeremy Messenger.
 	MATE is a desktop environment forked from the now-unmaintained
 	code base of GNOME 2, therefore it is basically a
-	replacement for GNOME 2.  It recommended for users wanting
-	to keep GNOME 2 as their desktop to switch since
+	replacement for GNOME 2.  Users wanting
+	to keep GNOME 2 as their desktop are advised to switch to MATE since
 	GNOME 2 will be replaced by GNOME 3 in the near
 	future.  This switch will be announced in advance, so people
 	will have time to move to MATE if they have not already.  The
@@ -998,7 +998,7 @@
     <help>
       <task>GNOME 2 ports still need to be sorted out to evaluate
 	which GNOME 2 components will be gone or be replaced with
-	their newer GNOME 3 versions.  This task is current halted
+	their newer GNOME 3 versions.  This task is currently halted
 	until we can get the documentation into a shape good enough to
 	gather the issues and document the migration, including how
 	to avoid the migration if the upgrade is not preferred.  (This
@@ -1031,7 +1031,7 @@
 	from the Intel team, and introduce support for the newest
 	hardware — in particular Haswell and ValleyView.  The
 	IvyBridge code will also be updated.  The addition of several
-	features, which are required in order to update X.Org and Mesa,
+	features which are required to update X.Org and Mesa
 	is also planned.</p>
     </body>
 
@@ -1169,7 +1169,7 @@
     </links>
 
     <body>
-      <p>At the November 2013 &os; Vendor Summit, some of the work was
+      <p>At the November 2013 &os; Vendor Summit, some work was
 	presented that Craig Rodrigues has been doing with Continuous
 	Integration and Testing at iXsystems.  Craig's presentation
 	described how iXsystems is using modern best practices for
@@ -1244,14 +1244,14 @@
 	change noticed.</p>
 
       <p>To better manage changes such as the <tt>WITH_NEW_XORG</tt> and
-	Cairo 1.12 changes mentioned above, we asked on the
+	the Cairo 1.12 changes mentioned above, we asked on the
 	<tt>freebsd-x11</tt> mailing-list if people are using
 	&os; 8.x on their desktop computers and why they do not
 	upgrade to &os; 9.x or 10.x.  So far, we received very few
 	answers to this.</p>
 
       <p>The Radeon KMS driver in &os; 10.x is now considered
-	stable, especially that integrated GPUs are now properly
+	stable, especially now that integrated GPUs are properly
 	initialized.  One of the next steps will be to merge this to
 	<tt>stable/9</tt>.</p>
 
@@ -1342,11 +1342,11 @@
 	replacement for the existing, quite old, virtual terminal
 	emulator called <tt>syscons(4)</tt>.  Initially motivated by the
 	lack of Unicode support in <tt>syscons(4)</tt>, the project was
-	later expanded to cover the new requirement to support Kernel
+	later expanded to cover the new requirement of supporting Kernel
 	Mode Switching (KMS).</p>
 
       <p>The project is now approaching completion and is ready for
-	wider testing as the related code was already merged to &os;
+	wider testing, as the related code was already merged to &os;
 	<tt>head</tt>.  Hence, <tt>vt(9)</tt> can be tested easily by
 	replacing the following two lines in the kernel config file:</p>
 
@@ -1378,7 +1378,7 @@ device vt_vga</pre>
 	<li>i386 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) — works.</li>
 	<li>IA64 — untested.</li>
 	<li>MIPS — untested.</li>
-	<li>PPC and PPC64 — Works, but without X.Org yet.</li>
+	<li>PPC and PPC64 — works, but without X.Org yet.</li>
 	<li>SPARC — works on certain hardware (e.g., Ultra 5).</li>
 	<li><tt>vesa(4)</tt> — in progress.</li>
 	<li>i386/amd64 nVidia driver — need testing.</li>
@@ -1469,7 +1469,7 @@ device vt_vga</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.  Currently, the daemon uses Transport Layer Security
 	(TLS) for communication, but only server-side certificates are
 	verified, based on the certificate's fingerprint.  The ongoing
@@ -1518,13 +1518,13 @@ device vt_vga</pre>
 
       <p>The &os; Port Management Team ensures that the &os; ports
 	developer community provides a Ports Collection that is
-	functional, stable, up-to-date and full-featured.  Its secondary
+	functional, stable, up-to-date, and full-featured.  Its secondary
 	responsibility is to coordinate among the committers and
-	developers who work on it.  As part of these efforts, we added 3
-	new committers, took in 3 commit bits for safe keeping, and
-	reinstated 1 commit bit in the fourth quarter of 2013.</p>
+	developers who work on it.  As part of these efforts, we added three
+	new committers, took in three commit bits for safe keeping, and
+	reinstated one commit bit in the fourth quarter of 2013.</p>
 
-      <p>Ongoing effort went into testing larger changes, as many as 8 a
+      <p>Ongoing effort went into testing larger changes, as many as eight a
 	week, including sweeping changes to the tree, moderization of
 	the infrastructure, and basic quality assurance (QA) runs.  Many
 	iterations of tests against <tt>10.0-RELEASE</tt> were run to
@@ -1746,7 +1746,7 @@ device vt_vga</pre>
 
       <p>Support in improving the experience of Wine on &os; is needed.
 	Key areas including fixing regressions, adding copy protection
-	scheme support and fixing regressions when using Wine under
+	scheme support, and fixing regressions when using Wine under
 	&os;/<tt>amd64</tt>.</p>
     </body>
 
@@ -1782,7 +1782,7 @@ device vt_vga</pre>
 	KDE/&os; Team have continued to improve the experience of KDE
 	software and Qt under &os;.</p>
 
-      <p>During last quarter, the team has kept most of the KDE and Qt
+      <p>During the last quarter, the team has kept most of the KDE and Qt
 	ports up-to-date, working on the following releases:</p>
 
       <ul>
@@ -1803,7 +1803,7 @@ device vt_vga</pre>
 	long time and we are very grateful for that.</p>
 
       <p>As usual, the team is always looking for more testers and
-	porters so please contact us or visit our home page (see links).
+	porters, so please contact us or visit our home page (see links).
 	It would be especially useful to have more helping hands on
 	tasks such as getting rid of the dependency on the defunct HAL
 	project and providing integration with KDE's Bluedevil Bluetooth
@@ -1861,12 +1861,12 @@ device vt_vga</pre>
 	&os; 10.x.</p>
 
       <p>It was a busy quarter for the src repository as well.  The Core
-	Team was happy to welcome Jordan K. Hubbard (<tt>jkh</tt>) back
+	Team was happy to welcome Jordan K. Hubbard (<tt>jkh</tt>) back,
 	who has recently returned to the &os; business, and joined
 	iXsystems as project manager and release engineer of FreeNAS.
-	In addition to this, there were 3 commit bits offered for new
-	developers, 2 committers were upgraded, 1 commit bit was taken
-	for safekeeping, and 1 src bit was reactivated.</p>
+	In addition to this, there were three commit bits offered for new
+	developers, two committers were upgraded, one commit bit was taken
+	for safekeeping, and one src bit was reactivated.</p>
     </body>
   </project>
 
@@ -1887,8 +1887,8 @@ device vt_vga</pre>
       <p>The GCC compiler in the &os; base system is on its way to
 	deprecation and is only used by some Tier-2 platforms at this
 	time.  While Clang is much better in many aspects, we still
-	cannot use in the base system all the new features that it
-	brings until we can drop GCC completely.  As a stop-gap
+	cannot use all the new features that it
+	brings in the base system until we can drop GCC completely.  As a stop-gap
 	solution, several bug fixes and features from Apple GCC and
 	other sources have been ported to our version of GCC 4.2.1
 	to make it more compatible with Clang.  &os;'s GCC has added
@@ -2090,9 +2090,9 @@ device vt_vga</pre>
 	I/O.  Otherwise it uses hardware virtualization extensions,
 	without the need for emulation.</p>
 
-      <p>After merging the changes in order to improve Xen PVHVM
+      <p>After merging the changes to improve Xen PVHVM
 	support, work has shifted on getting PVH DomU support on &os;.
-	Patches have been posted, and after a couple of rounds of review
+	Patches have been posted, and after a couple of rounds of review,
 	the series looks almost ready for merging into <tt>head</tt>.
 	Also, very initial patches for &os; PVH Dom0 support has been
 	posted.  So far the posted series only focuses on getting &os;


More information about the svn-doc-all mailing list