Grammar and typo fixes for the 2020Q2 status report.

Submitted by:	pauamma_gundo.com
Differential Revision:	https://reviews.freebsd.org/D25829

1 files changed, 18 insertions, 18 deletions

diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml
index 825b19fc99..8a5a41b06d 100644
--- a/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml
+++ b/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml
@@ -28,10 +28,10 @@
     <title>Introduction</title>
 <p>This report will be covering FreeBSD related projects between April and June, 
 and covers a diverse set of topics ranging from kernel updates over userland 
-and ports, as well to third-party work.
+and ports, as well as third-party work.
 </p>
 <p>Some highlights picked with the roll of a d100 include, but are not limited to,
-the ability to forcibly unmounting UFS when the underlying media becomes
+the ability to forcibly unmount UFS when the underlying media becomes
 inaccessible, added preliminary support for Bluetooth Low Energy, a introduction to the
 FreeBSD Office Hours, and a repository of software collections called potluck
 to be installed with the pot utility, as well as many many more things.
@@ -40,8 +40,8 @@ to be installed with the pot utility, as well as many many more things.
 </p>
 <p>Finally, on behalf of the quarterly team, I would like to extend my deepest 
 appreciation and thank you to salvadore@, who decided to take down his shingle.
-His contributions not just the quarterly reports themselves, but also the
-surrounding tooling to many-fold ease the work, are immeassurable.
+His contributions to not just the quarterly reports themselves, but also the
+surrounding tooling to many-fold ease the work, are immeasurable.
 </p>
 <p>We hope you find the report as interesting as we have,<br />
 Daniel Ebdrup Jensen (debdrup@), on behalf of the quarterly team.
@@ -71,7 +71,7 @@ legal entity.
 </p>
 <p>Here are some highlights of what we did to help FreeBSD last quarter:
 </p>
-<h3>COVID-19 Impact to the Foundation</h3>
+<h3>COVID-19 Impact on the Foundation</h3>
 
 <p>Like other organizations, we put policies in place for all of our staff members
 to work from home.  We also put a temporary ban on travel for staff members.
@@ -552,14 +552,14 @@ newly built results.
 The artifacts from the build jobs are archived in the artifact server for
 further testing and debugging needs.  The CI team members examine the
 failing builds and unstable tests and work with the experts in that area to
-fix the codes or adjust test infrastructure.  The details of these efforts
+fix the code or adjust test infrastructure.  The details of these efforts
 are available in the <a href='https://hackmd.io/@FreeBSD-CI'>weekly CI reports</a>.
 </p>
 <p>During the second quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
 </p>
 <p>Important changes:
 </p><ul>
-<li><p>All -test jobs will run tests under <code>/usr/tests</code>, previously only x86 architectures doing this. See the Continuous Integration on !x86 section in this report for more information.
+<li><p>All -test jobs will run tests under <code>/usr/tests</code>, previously only x86 architectures were doing this. See the Continuous Integration on !x86 section in this report for more information.
 </p></li>
 <li><p>Compression algorithm of disk images on the <a href='https://artifacts.ci.freebsd.org'>artifact server</a> has been changed to zstd to speed up compression and decompression.
 </p></li>
@@ -602,7 +602,7 @@ Work in progress:
 <li><p>Working with hosted CI providers to have better FreeBSD support
 </p>
 </li></ul>
-Please see freebsd-testing@ related tickets for more WIP information, and don't hesistate to join the effort!
+Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
 
 <p>Sponsor: The FreeBSD Foundation
 </p></body></project>
@@ -742,7 +742,7 @@ and posted to the official FreeBSD youtube channel.
 <url href='https://github.com/freebsd/freebsd-quarterly'>Git repository</url>
 </links>
 
-<body><p>The Quarterly Status Reports Team collects and publish the reports that you are
+<body><p>The Quarterly Status Reports Team collects and publishes the reports that you are
 reading right now.
 </p>
 <p>Many improvements have been done recently and thus we believe it is useful that
@@ -883,7 +883,7 @@ to the
 <a href='https://lists.freebsd.org/mailman/listinfo/freebsd-git'>FreeBSD-git mailing list</a>
 and test out the beta src, ports, and/or doc repositories.
 </p>
-<p>You are also welcome check out the wiki, issues, README and other documentation at the
+<p>You are also welcome to check out the wiki, issues, README and other documentation at the
 <a href='https://github.com/freebsd/git_conv'>Git conversion tooling repo</a>.
 </p>
 <p>We expect to be ready for the migration in the next quarter.
@@ -1288,7 +1288,7 @@ inaccessible. For example when a USB flash memory card hosting a
 UFS file system is unplugged.
 </p>
 <p>The rest of this report describes in more detail how forcible
-unmounts are done. Suprisingly, less than 500 lines of file
+unmounts are done. Surprisingly, less than 500 lines of file
 system code were added or changed.
 </p>
 <p>The strategy for handling disk I/O errors when soft updates are
@@ -1388,7 +1388,7 @@ Common changes include adding clock support and extending list of FDT compat str
 </contact>
 
 <body><p>The Intel Wireless cards are one of the most commonly used
-and ask for in FreeBSD notebooks.
+and asked for in FreeBSD notebooks.
 </p>
 <p>This project has three main goals:
 </p><ul>
@@ -1459,7 +1459,7 @@ using LA48 even if hardware can do LA57.
 <p>The most interesting part of the patch is the switch from boot paging
 mode to LA57.  Loaders, either legacy or UEFI, pass control to the
 kernel in Long Mode, which implies that the paging is turned on.  This
-neccessarily means that it is LA48 mode.  SDM states that paging mode
+necessarily means that it is LA48 mode.  SDM states that paging mode
 cannot be switched while Long Mode is active, so kernel has to create
 new page table structures, turn Long Mode off, then load new %cr3 and
 finally re-enable Long Mode.
@@ -1509,7 +1509,7 @@ hardware.
 
 <body><p>FreeBSD already provides excellent support for superpages, in a
 manner completely transparent to applications.  It tries to
-proactively prevent fragmentation, reserves contigous runs of the
+proactively prevent fragmentation, reserves contiguous runs of the
 physical pages for linear allocations in managed objects, and
 auto-promote runs of small pages when they form complete superpage.
 </p>
@@ -1527,8 +1527,8 @@ physically contiguous pages, with runs of specified size.  The mmap(2)
 syscall is aware of such objects, and if the requested mapping is
 properly aligned, it will be served by superpages.
 </p>
-<p>The new type of the shared memory objects are backed by modified
-a physical pager, which only allocates contigous physical memory.  The
+<p>The new type of the shared memory objects are backed by a modified
+physical pager, which only allocates contiguous physical memory.  The
 VM ensures that mappings of the objects are never split (clipped) on a
 non-superpage boundary.  The fault handler is specially optimized to
 be very fast by quickly installing the superpage PTE, and to avoid
@@ -1631,7 +1631,7 @@ superpage in NUMA configurations, and MAXCPU == 256 locks hashed by
 the page physical address for non-NUMA.  The end result is often
 undeserved lock aliasing causing pv list locks contention, since all
 4k pages in the 2M superpage share the same lock, and reservations
-typically cause adjasted pages to come from the same superpage.
+typically cause adjusted pages to come from the same superpage.
 </p>
 <p>The proposed patch creates a new kernel synchronization primitive
 called one byte mutex, which is embedded into the currently unused
@@ -1711,7 +1711,7 @@ Interested reader can find more detailed description in <a href='https://reviews
 </p>
 <p>Each route has a pointer to either nexthops or a nexthop group, decoupling lookup algorithm from the routing stack internals. Both nexthops and nexthop groups are immutable and use epoch(9)-backed reclamation.
 </p>
-<p>A pre-requisite for lockless routing lookup is the introduction of modular lookup framework, allowing to attach any longes-prefix-match algorithm implementation to any IPv4/IPv6 fib.
+<p>A pre-requisite for lockless routing lookup is the introduction of modular lookup framework, allowing to attach any longest-prefix-match algorithm implementation to any IPv4/IPv6 fib.
 </p>
 <p>Currently there are plans to use modified DIR-24-8 algorithm from DPDK for both IPv4 and IPv6 families as an example of base lockless implementation.
 </p>