Fixes courtesy @jrtc27.

src/features/c18n.md

@@ -71,10 +71,10 @@ cc -Wall -g -o helloworld helloworld.c -Wl,--dynamic-linker=/libexec/ld-elf-c18n
 ```
 
 You can confirm whether a binary uses the c18n run-time linker by inspecting
-its `INTERP` field using the `readelf -l` command:
+it using the `file` command:
 
 ```
-readelf -l helloworld
+file helloworld
 ```
 
 ## Tracing compartment-boundary crossings
@@ -105,7 +105,7 @@ important part of compartmentalization, internal software APIs are rarely well
 suited to be security boundaries without performing additional hardening.
 With this in mind:
 
- * Inspect the source code, ouput from `objdump`, and output from
+ * Inspect the source code, output from `objdump`, and output from
    `chericat` to assess the robustness of this compartmentalization.
  * Consider larger software architectural changes that will allow a library
    to be used more robustly when running within a computerment.

src/features/temporal.md

@@ -40,7 +40,6 @@ boot loader before any user processes start.
 
 ## Controlling revocation by binary or process
 
-
 You can forcefully enable or disable revocations for a specific binary or
 process
 with
@@ -71,7 +70,10 @@ revocation:
 malloc_revoke();
 ```
 
-Note that this can incur significant expense.
+Synchronous revocation on every call to `free()` can be configured using the
+`_RUNTIME_REVOCATION_EVERY_FREE_ENABLE` environmental variable.
+
+Note that synchronous revocation can incur extremely high expense.
 
 ## Monitoring revocation in processes