0.15.1 release notes: fix a few typos

Author: ee7

src/download/0.15.1/release-notes.html

@@ -1948,7 +1948,7 @@ <h1>0.15.1 Release Notes</h1>
     </ul>
     </li>
     <li>deleted <code>std.io.BitReader</code><ul>
-    <li>Bit reading should not be astracted at this layer; it just makes your hot loop harder to optimize. Tightly couple this code with your stream implementation.</li>
+    <li>Bit reading should not be abstracted at this layer; it just makes your hot loop harder to optimize. Tightly couple this code with your stream implementation.</li>
     </ul>
     </li>
     <li>deleted <code>std.io.BitWriter</code><ul>
@@ -1979,13 +1979,13 @@ <h1>0.15.1 Release Notes</h1>
     {#header_close#}
 
     {#header_open|Web Interface and Time Report#}
-    <p>Zig 0.14.0 included an experiemental web interface for the work-in-progress built-in fuzzer. In this version, that interface has been replaced with a more general web interface for the build system in general. This interface can be exposed using <code>zig build --webui</code>. When this option is passed, the <code>zig build</code> process will continue running even after the build completes.</p>
+    <p>Zig 0.14.0 included an experimental web interface for the work-in-progress built-in fuzzer. In this version, that interface has been replaced with a more general web interface for the build system in general. This interface can be exposed using <code>zig build --webui</code>. When this option is passed, the <code>zig build</code> process will continue running even after the build completes.</p>
     <p>The web interface is, by itself, relatively uninteresting: it merely shows the list of build steps and information about which are in progress, and has a button to manually trigger a rebuild (hence giving a possible alternative to the <code>zig build --watch</code> workflow). If <code>--fuzz</code> is passed to <code>zig build</code>, it also exposes the {#link|Fuzzer#} interface, which is mostly unchanged from 0.14.0.</p>
     <p>However, the web interface also exposes a new feature known as "time reports". By passing the new <code>--time-report</code> option to <code>zig build</code>, the web interface will include expandable information about the time taken to evaluate every step in the graph. In particular, any {#syntax#}std.Build.Step.Compile{#endsyntax#} in the graph will be associated with detailed information about which parts of the Zig compiler pipeline were fast and slow, and which individual files and declarations took the most time to semantically analyze, generate machine code for, and link into the binary.</p>
     <img src="release-notes/build-webui.png" alt="zig build web interface" style="width:100%">
     <p>This is a relatively advanced feature, but it can be very useful for determining parts of your code which are needlessly slowing down compilation, by opening the "Declarations" table and viewing the first few rows.</p>
     <img src="release-notes/build-webui-time-report.png" alt="compile step time report" style="width:100%">
-    <p>LLVM pass timing informations are also provided if the LLVM backend was used for the compilation.</p>
+    <p>LLVM pass timing information is also provided if the LLVM backend was used for the compilation.</p>
     {#header_close#}
 
     {#header_close#}