diff --git a/src/download/0.6.0/release-notes.html b/src/download/0.6.0/release-notes.html
index a02495257..8066c30de 100644
--- a/src/download/0.6.0/release-notes.html
+++ b/src/download/0.6.0/release-notes.html
@@ -2217,7 +2217,7 @@ <h1>0.6.0 Release Notes</h1>
     </p>
     <p>
     When one of these is accepted, it will be a compile error to copy some types.
-    to avoid copying, one can denote the capture value to make it a pointer:
+    To avoid copying, one can denote the capture value to make it a pointer:
     </p>
     {#code_begin|test|capture_aliasing#}
 const std = @import("std");
@@ -2456,7 +2456,7 @@ <h1>0.6.0 Release Notes</h1>
 
     {#header_open|Slicing with Comptime Indexes#}
     <p>
-    When slicing and the length is comptime-known, the expression type is now
+    When slicing where the length is comptime-known, the expression type is now
     a single-item pointer to array {#syntax#}*[N]T{#endsyntax#} .
     Prior to this change an error-prone {#syntax#}@ptrCast{#endsyntax#} was required.
     </p>
@@ -2657,7 +2657,7 @@ <h1>0.6.0 Release Notes</h1>
         does not require an allocator.
       </li>
       <li>
-        Sebsatian Keller added std.math constants such as log2e and sqrt2.
+        Sebastian Keller added std.math constants such as log2e and sqrt2.
         Note that with <a href="https://github.com/ziglang/zig/issues/425">#425</a> solved these would not be needed, and would be removed.
       </li>
     </ul>
@@ -2680,7 +2680,7 @@ <h1>0.6.0 Release Notes</h1>
     when the time spent in the critical section is minimal and acquiring/releasing is done
     frequently. The implementation chosen for this was that of lock_futex.go from Golang 1.13
     as it provides a nice balance between spinning and deciding to block (another possibility
-    could be rust/webkit `parking_lot`). Because this implementation only needs a futex interface,
+    could be rust/webkit <code>parking_lot</code>). Because this implementation only needs a futex interface,
     it can be reused:
     </p>
     <p><strong>2) Parker API</strong></p>
@@ -2984,7 +2984,7 @@ <h1>0.6.0 Release Notes</h1>
     The good news:
     </p>
     <ul>
-      <li>The new API is objectively simpler and more ergonomic.</li>
+      <li>The new API is simpler and more ergonomic.</li>
       <li>Empirically, it produces significantly faster runtime code.</li>
       <li>It works cleanly with {#link|Async I/O#}.</li>
     </ul>
@@ -3041,7 +3041,7 @@ <h1>0.6.0 Release Notes</h1>
     {#code_end#}
     <p>
     InStream, OutStream, and SeekableStream were already generic
-    across error sets, it's not really worse to make them generic across the
+    across error sets; it's not really worse to make them generic across the
     vtable as well, which is what this change did.
     </p>
     <p>
@@ -3115,9 +3115,9 @@ <h1>0.6.0 Release Notes</h1>
       <li>Various APIs and implementations improved to take advantage of directory handles.</li>
       <li>Error sets of various functions are improved to no longer have some kinds of errors, such
         as {#syntax#}error.OutOfMemory{#endsyntax#}, or in the case of deleting a file, {#syntax#}error.NoSpaceLeft{#endsyntax#}.</li>
-      <li>The new convention for APIs with null-terminated path parameters is the 'Z' suffix rather than 'C' suffix.</li>
-      <li>Some APIs are modified to take "options" structs which have default fields values.</li>
-      <li>inode number / file index is exposed into File.Stat.</li>
+      <li>The new convention for APIs with null-terminated path parameters is a 'Z' suffix rather than a 'C' suffix.</li>
+      <li>Some APIs are modified to take "options" structs which have default field values.</li>
+      <li>inode number / file index is exposed in File.Stat.</li>
       <li>Cross-platform file locking flags are supported.</li>
       <li>fs.File supports setEndPos to grow/shrink the file size as needed. (<a href="https://github.com/ziglang/zig/issues/4716">#4716</a>)</li>
       <li>Filesystem APIs now integrate with {#link|Async I/O#}, including automatically performing
@@ -3293,7 +3293,7 @@ <h1>0.6.0 Release Notes</h1>
   zen
   uefi</code></pre>
     <p>This list was the list of targets that LLVM supported +
-    <a href="https://github.com/AndreaOrru/zen">zen</a>(a hobby OS not maintained for over 1 year) +
+    <a href="https://github.com/AndreaOrru/zen">zen</a> (a hobby OS not maintained for over 1 year) +
     UEFI.
     </p>
     <p>
@@ -3371,7 +3371,7 @@ <h1>0.6.0 Release Notes</h1>
 }
     {#code_end#}
     <p>
-    {#syntax#}system{#endsyntax#} in this refered to:
+    Where {#syntax#}system{#endsyntax#} referred to:
     </p>
     {#code_begin|syntax#}
 /// When linking libc, this is the C API. Otherwise, it is the OS-specific system interface.
@@ -3388,7 +3388,7 @@ <h1>0.6.0 Release Notes</h1>
 };
     {#code_end#}
     <p>
-    {#syntax#}else => struct{},{#endsyntax#} is modified to look for
+    Now, {#syntax#}else => struct{}{#endsyntax#} is modified to look for
     {#syntax#}@import("root").os{#endsyntax#} if it is provided.
     With this modification, as long as the OS package defines all the constants (such as
     {#syntax#}fd_t{#endsyntax#} and {#syntax#}EISDIR{#endsyntax#}), then
@@ -3413,7 +3413,7 @@ <h1>0.6.0 Release Notes</h1>
     <p>
     Now that this is implemented, Zig has first class support for all operating systems.
     The main difference between upstream-recognized OSes and "other" OSes would be where the support
-    is maintained - upstream zig std lib, or in a third party "OS layer" package.
+    is maintained: in zig's std lib, or in a third party "OS layer" package.
     </p>
     <p>
     With this new feature, upstream support for Zen hobby OS is removed.
@@ -3474,7 +3474,7 @@ <h1>0.6.0 Release Notes</h1>
         uses {#link|Sentinel-Terminated Pointers#}.</li>
       <li>Added {#syntax#}std.mem.span{#endsyntax#}.</li>
       <li>Added {#syntax#}std.mem.spanZ{#endsyntax#}.</li>
-      <li>Added {#syntax#}std.mem.zeros{#endsyntax#} which zero-initializes types which have
+      <li>Added {#syntax#}std.mem.zeroes{#endsyntax#} which zero-initializes types which have
         well-defined memory layouts. (<a href="https://github.com/ziglang/zig/issues/4544">#4544</a>)</li>
       <li>Added {#syntax#}std.mem.Allocator.allocSentinel{#endsyntax#}.</li>
       <li>Added {#syntax#}std.mem.indexOfSentinel{#endsyntax#}.</li>
@@ -3824,7 +3824,7 @@ <h1>0.6.0 Release Notes</h1>
     Bootstrapping is not to be confused with {#link|self-hosting|Self-Hosted Compiler Progress#}.
     </p>
     <p>
-    I forgot to mention in the blog post, when you don't pass any optimization flags to
+    I forgot to mention in the blog post that when you don't pass any optimization flags to
     <code>zig cc</code>, Zig determines that
     <a href="https://ziglang.org/documentation/0.6.0/#Debug">Debug Mode</a> is appropriate,
     and enables <a href="https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html">Clang's UBSAN</a>.
@@ -4565,7 +4565,7 @@ <h1>0.6.0 Release Notes</h1>
       <li>Exported variables now respect linkage.</li>
       <li>Alexandros Naskos fixed slicing of C pointers to no longer produce {#syntax#}allowzero{#endsyntax#} slices. Instead they insert a runtime assertion. (<a href="https://github.com/ziglang/zig/issues/4462">#4462</a>)</li>
       <li>Alexandros Naskos improved made the std lib VDSO code more robust and it now operates successfully inside Windows Subsystem for Linux. (<a href="https://github.com/ziglang/zig/issues/3997">#3997</a>)</li>
-      <li>LemonBoy improved arrray subscripts to properly type coerce to {#syntax#}usize{#endsyntax#}. (<a href="https://github.com/ziglang/zig/issues/4169">#4169</a>)</li>
+      <li>LemonBoy improved array subscripts to properly type coerce to {#syntax#}usize{#endsyntax#}. (<a href="https://github.com/ziglang/zig/issues/4169">#4169</a>)</li>
       <li>LemonBoy implemented a compile error for comparison between enum literal and untagged enum. (<a href="https://github.com/ziglang/zig/issues/4770">#4770</a>)</li>
       <li>xackus fixed an overflow in {#syntax#}std.fmt.parseFloat{#endsyntax#} (<a href="https://github.com/ziglang/zig/issues/4845">#4845</a>)</li>
       <li>Michaël Larouche fixed adler32 returning incorrect value with large input.</li>