From 49677088a35e9713584b45e4d1a99e1cc7f20d87 Mon Sep 17 00:00:00 2001
From: Bruce Mitchener <bruce.mitchener@gmail.com>
Date: Sun, 14 Jul 2024 00:12:57 +0700
Subject: [PATCH] Fix typos.

---
 README.md     | 6 +++---
 imports.md    | 2 +-
 wit/types.wit | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 9780c6c..73dd4d5 100644
--- a/README.md
+++ b/README.md
@@ -55,7 +55,7 @@ semantics of path lookup, and the semantics of files, directories, and
 symlinks, and the constraints on filesystem paths, is host-dependent.
 
 WASI filesystem is not intended to be used as a virtual API for accessing
-arbitary resources. Unix's "everything is a file" philosophy is in conflict
+arbitrary resources. Unix's "everything is a file" philosophy is in conflict
 with the goals of supporting modularity and the principle of least authority.
 
 Many of the ideas related to doing capability-based filesystem sandboxing with
@@ -94,7 +94,7 @@ fn write_hello_world_to_a_file(dir: Descriptor) -> Result<(), Errno> {
     while !view.is_empty() {
         let num_written = file.pwrite(view.to_owned(), 0)?;
         offset += num_written;
-        view = &view[num_writen..];
+        view = &view[num_written..];
     }
     // The file descriptor is closed when it's dropped!
 }
@@ -141,7 +141,7 @@ case-insensitivity on a case-sensitive filesystem, are both tricky to do.
 
 One issue is that case insensitivity depends on a Unicode version, so the
 details can differ between different case-insensitive platforms. Another
-issue is tha WASI filesystem in general can't assume it has exclusive access
+issue is the WASI filesystem in general can't assume it has exclusive access
 to the filesystem, so approaches that involve checking for files with names
 that differ only by case can race with other processes creating new files.
 
diff --git a/imports.md b/imports.md
index 660858b..f3e9b7b 100644
--- a/imports.md
+++ b/imports.md
@@ -569,7 +569,7 @@ requirement.</p>
 </li>
 <li>
 <p><a name="descriptor_flags.requested_write_sync"></a><code>requested-write-sync</code>: </p>
-<p>Requests that reads be performed at the same level of integrety
+<p>Requests that reads be performed at the same level of integrity
 requested for writes. This is similar to `O_RSYNC` in POSIX.
 <p>The precise semantics of this operation have not yet been defined for
 WASI. At this time, it should be interpreted as a request, and not a
diff --git a/wit/types.wit b/wit/types.wit
index 4900ae2..d061d5f 100644
--- a/wit/types.wit
+++ b/wit/types.wit
@@ -83,7 +83,7 @@ interface types {
         /// WASI. At this time, it should be interpreted as a request, and not a
         /// requirement.
         data-integrity-sync,
-        /// Requests that reads be performed at the same level of integrety
+        /// Requests that reads be performed at the same level of integrity
         /// requested for writes. This is similar to `O_RSYNC` in POSIX.
         ///
         /// The precise semantics of this operation have not yet been defined for