Editing

2 files changed, 4 insertions, 4 deletions

diff --git a/docs/spec/system.html b/docs/spec/system.html
index 2c6c3321..3da59147 100644
--- a/docs/spec/system.html
+++ b/docs/spec/system.html
@@ -240,7 +240,7 @@
 </tr>
 </tbody>
 </table>
-<h2 id="timing">Timing</h2>
+<h2 id="time">Time</h2>
 <table>
 <thead>
 <tr>
@@ -273,5 +273,5 @@
 </table>
 <p>All times are measured in seconds.</p>
 <p>The <a href="https://en.wikipedia.org/wiki/Unix_time">Unix epoch</a> is 1970-01-01 00:00:00 UTC. <code><span class='Function'>•UnixTime</span></code> is intended for absolute time measurement and should be implemented with the method that gives the most accurate result at any given time. <code><span class='Function'>•MonoTime</span></code> is intended for relative measurement and should use the method that gives the most precise time differences over the course of the program. Its return value must never decrease between calls.</p>
-<p><code><span class='Modifier'>•_timed</span></code> returns the total time taken divided by the number of function calls, including the overhead required for the outer loop that counts iterations (which will typically by negligible in comparison to the BQN code).</p>
+<p><code><span class='Modifier'>•_timed</span></code> returns the total time taken divided by the number of function calls, including the overhead required for the outer loop that counts iterations (which will typically be negligible in comparison to the BQN code).</p>
 <p>More accurately the modifier <code><span class='Modifier2'>•_maxTime_</span></code> <em>may</em> fail if execution of <code><span class='Function'>𝔽</span></code> takes over <code><span class='Value'>𝕨</span><span class='Function'>𝔾</span><span class='Value'>𝕩</span></code> seconds, and should fail as quickly as it is practically able to. The most likely way to implement this modifier is to interrupt execution at the given time. If <code><span class='Function'>𝔽</span></code> completes before the interrupt there is no need to measure the amount of time it actually took.</p>
diff --git a/spec/system.md b/spec/system.md
index 11814fea..61f71a60 100644
--- a/spec/system.md
+++ b/spec/system.md
@@ -103,7 +103,7 @@ Each function in this section is monadic.
 | Left partial  |  6   | `𝕗,𝕣`
 | Right partial |  7   | `  𝕣,𝕘`
 
-## Timing
+## Time
 
 | Name          | Summary
 |---------------|--------------------------
@@ -117,6 +117,6 @@ All times are measured in seconds.
 
 The [Unix epoch](https://en.wikipedia.org/wiki/Unix_time) is 1970-01-01 00:00:00 UTC. `•UnixTime` is intended for absolute time measurement and should be implemented with the method that gives the most accurate result at any given time. `•MonoTime` is intended for relative measurement and should use the method that gives the most precise time differences over the course of the program. Its return value must never decrease between calls.
 
-`•_timed` returns the total time taken divided by the number of function calls, including the overhead required for the outer loop that counts iterations (which will typically by negligible in comparison to the BQN code).
+`•_timed` returns the total time taken divided by the number of function calls, including the overhead required for the outer loop that counts iterations (which will typically be negligible in comparison to the BQN code).
 
 More accurately the modifier `•_maxTime_` *may* fail if execution of `𝔽` takes over `𝕨𝔾𝕩` seconds, and should fail as quickly as it is practically able to. The most likely way to implement this modifier is to interrupt execution at the given time. If `𝔽` completes before the interrupt there is no need to measure the amount of time it actually took.