diff --git a/archive/faq.html b/archive/faq.html
index 94741437..f032b22f 100644
--- a/archive/faq.html
+++ b/archive/faq.html
@@ -277,7 +277,7 @@ <H2>
   </H2>
   <UL>
     <LI>
-      <A HREF="#background">FontForge's grey background distesses me. How do I
+      <A HREF="#background">FontForge's grey background distresses me. How do I
       change it?</A>
     <LI>
       <A HREF="#fontsize">The fonts FontForge uses in its GUI are too small (too
@@ -667,7 +667,7 @@ <H2>
 	</TR>
       </TABLE>
       <P>
-      Mostly because I don't thnk that way. I don't plan things out, I have a vague
+      Mostly because I don't think that way. I don't plan things out, I have a vague
       idea where I want to go and I explore in that direction.
       <P>
       Consider python scripting. I decided to add python to fontforge. I found
@@ -846,7 +846,7 @@ <H2>
 	      Info-&gt;OS/2-&gt;Metrics</A>.
 	    <LI>
 	      On windows<BR>
-	      Line spacing is supposed to be set to the Typo Ascent/Typo Desent values
+	      Line spacing is supposed to be set to the Typo Ascent/Typo Descent values
 	      specified in the OS/2 table. And these in turn are supposed to sum to the
 	      emsize. (FontForge sets these values to the ascent/descent values you specify
 	      for your font). Unfortunately most windows applications don't follow this
@@ -860,7 +860,7 @@ <H2>
 	      (The clipping region should be bigger than the bounding box if a GPOS lookup
 	      could move a glyph so that it extended beyond the bounding box (mark to base
 	      is likely to cause problems). I'm not sure how this applies to cursive
-	      positioning in Urdu where GPOS lookups can make lines arbetrarily tall)
+	      positioning in Urdu where GPOS lookups can make lines arbitrarily tall)
 	      <P>
 	      MicroSoft has added a redundant bit to the OS/2 table, which essentially
 	      tells applications they should follow the standard and use the Typographic
@@ -953,7 +953,7 @@ <H2>
 	  (like the latin alphabet) then 192Mb is more than enough.
 	<LI>
 	  If you are doing serious editing of CJK fonts then 512Mb is on the low end
-	  of useablity.
+	  of usability.
       </UL>
       <P>
       FontForge requires a color (or grey-scale) monitor -- black &amp; white will
diff --git a/archive/pfaeditmath.html b/archive/pfaeditmath.html
index 3063e847..d28d50ab 100644
--- a/archive/pfaeditmath.html
+++ b/archive/pfaeditmath.html
@@ -593,7 +593,7 @@ <H3>
   we will end up with one closed contour. While if we start with a closed contour
   we will end up with two closed contours (one on the inside, and one on the
   outside). Unless there are places where the curve doubles back on itself,
-  then when can get arbetrarily many closed contours.
+  then when can get arbitrarily many closed contours.
   <H3>
     An elliptical pen
   </H3>
diff --git a/docs/faq.html b/docs/faq.html
index ac253498..5e050ab7 100644
--- a/docs/faq.html
+++ b/docs/faq.html
@@ -174,7 +174,7 @@ <h2>Image file questions<a class="headerlink" href="#image-file-questions" title
 <section id="random-questions">
 <h2>Random questions<a class="headerlink" href="#random-questions" title="Permalink to this heading">¶</a></h2>
 <ul class="simple">
-<li><p><a class="reference internal" href="#faq-background"><span class="std std-ref">FontForge’s grey background distesses me. How do I change it?</span></a></p></li>
+<li><p><a class="reference internal" href="#faq-background"><span class="std std-ref">FontForge’s grey background distresses me. How do I change it?</span></a></p></li>
 <li><p><a class="reference internal" href="#faq-fontsize"><span class="std std-ref">The fonts FontForge uses in its GUI are too small (too big) how do I change them?</span></a></p></li>
 <li><p><a class="reference internal" href="#faq-monospace"><span class="std std-ref">How do I mark a font as monospaced?</span></a></p></li>
 <li><p><a class="reference internal" href="#faq-new-encoding"><span class="std std-ref">How do I tell fontforge about a new encoding?</span></a></p></li>
@@ -443,7 +443,7 @@ <h2>Random questions<a class="headerlink" href="#random-questions" title="Permal
 </div>
 <p class="attribution">—<em>The Lady’s not for Burning</em> – Christopher Fry</p>
 </div></blockquote>
-<p>Mostly because I don’t thnk that way. I don’t plan things out, I have a vague
+<p>Mostly because I don’t think that way. I don’t plan things out, I have a vague
 idea where I want to go and I explore in that direction.</p>
 <p>Consider python scripting. I decided to add python to fontforge. I found that
 meant it became easier to design a mechanism so users could create their own
@@ -584,7 +584,7 @@ <h2>Random questions<a class="headerlink" href="#random-questions" title="Permal
 <a class="reference internal" href="ui/dialogs/fontinfo.html#fontinfo-ttf-metrics"><span class="std std-ref">Element-&gt;Font Info-&gt;OS/2-&gt;Metrics</span></a>.</p>
 </li>
 <li><p>On windows</p>
-<p>Line spacing is supposed to be set to the Typo Ascent/Typo Desent values
+<p>Line spacing is supposed to be set to the Typo Ascent/Typo Descent values
 specified in the OS/2 table. And these in turn are supposed to sum to the
 emsize. (FontForge sets these values to the ascent/descent values you specify
 for your font). Unfortunately most windows applications don’t follow this
@@ -596,7 +596,7 @@ <h2>Random questions<a class="headerlink" href="#random-questions" title="Permal
 <p>(The clipping region should be bigger than the bounding box if a GPOS lookup
 could move a glyph so that it extended beyond the bounding box (mark to base
 is likely to cause problems). I’m not sure how this applies to cursive
-positioning in Urdu where GPOS lookups can make lines arbetrarily tall)</p>
+positioning in Urdu where GPOS lookups can make lines arbitrarily tall)</p>
 <p>MicroSoft has added a redundant bit to the OS/2 table, which essentially
 tells applications they should follow the standard and use the Typographic
 linespacing fields. This bit is called UseTypoMetrics in OpenType, and in
@@ -675,7 +675,7 @@ <h2>Random questions<a class="headerlink" href="#random-questions" title="Permal
 <li><p>If you are interested in scripts with no more than few hundred simple glyphs
 (like the latin alphabet) then 192Mb is more than enough.</p></li>
 <li><p>If you are doing serious editing of CJK fonts then 512Mb is on the low end of
-useablity.</p></li>
+usability.</p></li>
 </ul>
 <p>FontForge requires a color (or grey-scale) monitor – black &amp; white will not
 suffice.</p>
diff --git a/docs/old/ja/faq.html b/docs/old/ja/faq.html
index c2b34301..5e4f1a06 100644
--- a/docs/old/ja/faq.html
+++ b/docs/old/ja/faq.html
@@ -621,7 +621,7 @@ <H2>
 	      ラインスペーシングは&lsquo;hhea&rsquo;テーブルのアセンダとディセンダの値によって設定されます。これは、裏を返せばフォントのバウンディングボックスの値に設定されるということです。これは賢い選択ではありません。
 	    <LI>
 <!--	      On windows<BR>
-	      Line spacing is supposed to be set to the Typo Ascent/Typo Desent values
+	      Line spacing is supposed to be set to the Typo Ascent/Typo Descent values
 	      specified in the OS/2 table. And these in turn are supposed to sum to the
 	      emsize. (FontForge sets these values to the ascent/descent values you specify
 	      for your font). Unfortunately most windows applications don't follow this
@@ -635,7 +635,7 @@ <H2>
 <!--	      (The clipping region should be bigger than the bounding box if a GPOS lookup
 	      could move a glyph so that it extended beyond the bounding box (mark to base
 	      is likely to cause problems). I'm not sure how this applies to cursive
-	      positioning in Urdu where GPOS lookups can make lines arbetrarily tall) -->
+	      positioning in Urdu where GPOS lookups can make lines arbitrarily tall) -->
 	      (GPOS の位置指定によってグリフがバウンディングボックスからはみ出る位置に移動する場合は、クリッピング領域はバウンディングボックスよりも大きくする必要があります (マークから基底文字への参照が問題を起こすようです)。GPOS によって行がいくらでも高くなる可能性があるウルドゥー語の筆記体ではこれがどのように当てはまるのかについてはよく分かりません)
 	    <LI>
 <!--	      On linux<BR>
@@ -717,7 +717,7 @@ <H2>
 	  (ラテンアルファベットのような) たかだか数百個の単純なグリフを含む用字系にのみ興味があるならば、192MB で十分すぎるでしょう。
 	<LI>
 <!--	  If you are doing serious editing of CJK fonts then 512Mb is on the low end
-	  of useablity. -->
+	  of usability. -->
 	  CJK フォントの本格的に編集を行うなら、512MB が使いものになる最低限の容量でしょう。
       </UL>
       <P>