docs: fix typos

Author: erxclau

doc-tools/doc-pages/src/pages/PageConceptRendering.tsx

@@ -78,7 +78,7 @@ export default function PageConceptRendering() {
           The great benefit of using <Bold>explicitly</Bold> this composite
           rendering architecture is that the engine and configuration can be put
           near the top of your App to factor the cost of instantiating the
-          engine. This is <Bold>especially usefull</Bold> for apps which will
+          engine. This is <Bold>especially useful</Bold> for apps which will
           render hundreds to thousands of small snippets such as chat apps.
         </Admonition>
         <Paragraph>

doc-tools/doc-pages/src/pages/PageFAQ.tsx

@@ -85,7 +85,7 @@ export default function PageFAQ() {
         </Section>
         <Section title="Aren't there better renderers for tables?">
           <Paragraph>
-            Sure! The default renderer is very limitted. Check-out{' '}
+            Sure! The default renderer is very limited. Check-out{' '}
             <Hyperlink url="https://github.com/native-html/plugins/tree/master/packages/table-plugin#readme">
               @native-html/table-plugin
             </Hyperlink>{' '}

doc-tools/doc-pages/src/pages/PageGuideDomTampering.tsx

@@ -240,7 +240,7 @@ export default function PageGuideDomTampering() {
           The general recommendation for this three-layers rendering
           architecture is that the engine and configuration should be put near
           the top of your App to factor the cost of instantiating the engine.
-          This is especially usefull for apps which will render hundreds to
+          This is especially usefuld for apps which will render hundreds to
           thousands of small snippets such as chat apps.
         </ListItem>
       </List>

doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx

@@ -82,7 +82,7 @@ export default function PageReinventTheWheel() {
         <Paragraph>
           To do so, we will need an HTML parsing library which will give us some
           sort of proxy DOM representation of the HTML source. In this very
-          example, we will use <RefHtmlparser2 /> libarary:
+          example, we will use <RefHtmlparser2 /> library:
         </Paragraph>
         <SourceDisplay
           lang="jsx"
@@ -116,7 +116,7 @@ export default function PageReinventTheWheel() {
         </List>
         <Paragraph>
           Although the <InlineCode>renderTextNode</InlineCode> implementation is
-          pretty straightforward,
+          pretty straightforward,{' '}
           <InlineCode>renderElement</InlineCode> has some conditional logic to
           render the element either in a React Native{' '}
           <RefRNSymbol name="Text" /> or <RefRNSymbol name="View" />. This is to
@@ -126,7 +126,7 @@ export default function PageReinventTheWheel() {
         </Paragraph>
         <Admonition type="note">
           We allude to the DOM an DOM nodes while <RefHtmlparser2 /> only
-          provides a substet of the DOM API for lightweightness!
+          provides a subset of the DOM API for lightweightness!
         </Admonition>
       </Chapter>
       <Chapter title="Discussion">