From ba02d3143889769dd6eab23df829ae4db8100b97 Mon Sep 17 00:00:00 2001
From: Eric Lau <44459660+erxclau@users.noreply.github.com>
Date: Sun, 25 Dec 2022 07:36:26 -0500
Subject: [PATCH] docs: fix typos
---
doc-tools/doc-pages/src/pages/PageConceptRendering.tsx | 2 +-
doc-tools/doc-pages/src/pages/PageFAQ.tsx | 2 +-
doc-tools/doc-pages/src/pages/PageGuideDomTampering.tsx | 2 +-
doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx | 6 +++---
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc-tools/doc-pages/src/pages/PageConceptRendering.tsx b/doc-tools/doc-pages/src/pages/PageConceptRendering.tsx
index a08a0b273..20ab7a31b 100644
--- a/doc-tools/doc-pages/src/pages/PageConceptRendering.tsx
+++ b/doc-tools/doc-pages/src/pages/PageConceptRendering.tsx
@@ -78,7 +78,7 @@ export default function PageConceptRendering() {
The great benefit of using explicitly 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 especially usefull for apps which will
+ engine. This is especially useful for apps which will
render hundreds to thousands of small snippets such as chat apps.
diff --git a/doc-tools/doc-pages/src/pages/PageFAQ.tsx b/doc-tools/doc-pages/src/pages/PageFAQ.tsx
index 0deb37a26..6e22bc52c 100644
--- a/doc-tools/doc-pages/src/pages/PageFAQ.tsx
+++ b/doc-tools/doc-pages/src/pages/PageFAQ.tsx
@@ -85,7 +85,7 @@ export default function PageFAQ() {
- Sure! The default renderer is very limitted. Check-out{' '}
+ Sure! The default renderer is very limited. Check-out{' '}
@native-html/table-plugin
{' '}
diff --git a/doc-tools/doc-pages/src/pages/PageGuideDomTampering.tsx b/doc-tools/doc-pages/src/pages/PageGuideDomTampering.tsx
index 88a2db41e..71193b7c8 100644
--- a/doc-tools/doc-pages/src/pages/PageGuideDomTampering.tsx
+++ b/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.
diff --git a/doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx b/doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx
index add8f60e6..229c68006 100644
--- a/doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx
+++ b/doc-tools/doc-pages/src/pages/PageReinventTheWheel.tsx
@@ -82,7 +82,7 @@ export default function PageReinventTheWheel() {
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 libarary:
+ example, we will use library:
Although the renderTextNode implementation is
- pretty straightforward,
+ pretty straightforward,{' '}
renderElement has some conditional logic to
render the element either in a React Native{' '}
or . This is to
@@ -126,7 +126,7 @@ export default function PageReinventTheWheel() {
We allude to the DOM an DOM nodes while only
- provides a substet of the DOM API for lightweightness!
+ provides a subset of the DOM API for lightweightness!