NuttxPortingGuide.html edited online with Bitbucket

Documentation/NuttxPortingGuide.html

@@ -422,7 +422,7 @@
   </li>
   <li>
     <i>Chip/SoC specific files</i>.
-    Each processor processor architecture is embedded in chip or <i>System-on-a-Chip</i> (SoC) architecture.
+    Each processor architecture is embedded in chip or <i>System-on-a-Chip</i> (SoC) architecture.
     The full chip architecture includes the processor architecture plus chip-specific interrupt logic,
     clocking logic, general purpose I/O (GPIO) logic, and specialized, internal peripherals (such as UARTs, USB, etc.).
     <p>
@@ -1531,7 +1531,7 @@ The specific environmental definitions are unique for each board but should incl
       The definitions in that header file provide the common interface between NuttX and the architecture-specific implementation in <code>arch/</code>.
     </p>
     <blockquote><small>
-      <code>up_</code> is supposed to stand for microprocessor; the <code>u</code> is like the Greek letter micron: <i>µ</i>.    So it would be <code>µP</code> which is a common shortening of the word microprocessor.  I don't like that name very much.  I wish I would have used a more obvious prefix like <code>arch_</code> instead -- then I would not have to answer this question so often.
+      <code>up_</code> is supposed to stand for microprocessor; the <code>u</code> is like the Greek letter micron: <i><EFBFBD></i>.    So it would be <code><EFBFBD>P</code> which is a common shortening of the word microprocessor.  I don't like that name very much.  I wish I would have used a more obvious prefix like <code>arch_</code> instead -- then I would not have to answer this question so often.
     </small></blockquote>
   </li>
   <li>