diff --git a/doc/schema/objects/permanode.txt b/doc/schema/objects/permanode.txt
index c85e90188..0bcfd863d 100644
--- a/doc/schema/objects/permanode.txt
+++ b/doc/schema/objects/permanode.txt
@@ -6,7 +6,7 @@ object it must have no mutable state itself.
  "camliType": "permanode",
 
  // Required.  Any random string, to force the sha1 of this
- // node to be unique.  Note that the date in the ASCI-armored
+ // node to be unique.  Note that the date in the ASCII-armored
  // GPG JSON signature will already help it be unique, so this
  // doesn't need to be a great random.
  "random": "615e05c68c8411df81a2001b639d041f"
diff --git a/website/content/docs/terms b/website/content/docs/terms
index 001be0671..3104f2939 100644
--- a/website/content/docs/terms
+++ b/website/content/docs/terms
@@ -72,7 +72,7 @@ href="http://en.wikipedia.org/wiki/File_format#Magic_number">number</a>
 by which a Camli search server can quickly recognize and index schema blobs.
 
 <p>The recommended way to serialize your own Camli schema blobs is to
-use any exiting JSON serialization library to serialize an object
+use any existing JSON serialization library to serialize an object
 <em>without</em> the <tt>camliVersion</tt> key, and then manually remove
 the initial byte of the blob (the <tt>{</tt>) and prepend the required
 header:</p>
@@ -132,7 +132,7 @@ header:</p>
 <dd>since an object is mutable and Camlistore is primarily content-addressed,
   the question arises how you could have a stable reference to something that's
   changing.  Camlistore solves this with the concept of a <em>permanode</em>.
-  Link a permalink on the web, a permanode is a stable link to a Camli object.
+  Like a permalink on the web, a permanode is a stable link to a Camli object.
 
   <p>A permanode is simply a <a href="/docs/json-signing">signed</a>
      schema blob with no data inside that would be interesting to