You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by gi...@apache.org on 2023/11/25 00:23:41 UTC

(nuttx-website) branch asf-site updated: Publishing web: 36ddd7c60a8230335eda886c909bc938739114a2 docs: 3ed629274e803ccc14895afd7a67757b7f424d35

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/nuttx-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 8c0d7cac Publishing web: 36ddd7c60a8230335eda886c909bc938739114a2 docs: 3ed629274e803ccc14895afd7a67757b7f424d35
8c0d7cac is described below

commit 8c0d7cacb260d8f5e2592976114d5805fadf8c76
Author: Alin Jerpelea <al...@sony.com>
AuthorDate: Sat Nov 25 00:13:22 2023 +0000

    Publishing web: 36ddd7c60a8230335eda886c909bc938739114a2 docs: 3ed629274e803ccc14895afd7a67757b7f424d35
---
 content/docs/10.0.0/index.html                                    | 2 +-
 content/docs/10.0.0/searchindex.js                                | 2 +-
 content/docs/10.0.1/index.html                                    | 2 +-
 content/docs/10.0.1/searchindex.js                                | 2 +-
 content/docs/10.1.0/index.html                                    | 2 +-
 content/docs/10.1.0/searchindex.js                                | 2 +-
 content/docs/10.2.0/index.html                                    | 2 +-
 content/docs/10.2.0/searchindex.js                                | 2 +-
 content/docs/10.3.0/index.html                                    | 2 +-
 content/docs/10.3.0/searchindex.js                                | 2 +-
 content/docs/11.0.0/index.html                                    | 2 +-
 content/docs/11.0.0/searchindex.js                                | 2 +-
 content/docs/12.0.0/index.html                                    | 2 +-
 content/docs/12.0.0/searchindex.js                                | 2 +-
 content/docs/12.1.0/index.html                                    | 2 +-
 content/docs/12.1.0/searchindex.js                                | 2 +-
 content/docs/12.2.0/index.html                                    | 2 +-
 content/docs/12.2.0/searchindex.js                                | 2 +-
 content/docs/12.2.1/index.html                                    | 2 +-
 .../platforms/xtensa/esp32/boards/esp32-audio-kit/index.html      | 2 +-
 .../12.2.1/platforms/xtensa/esp32/boards/esp32-devkitc/index.html | 2 +-
 content/docs/12.2.1/searchindex.js                                | 2 +-
 content/docs/12.3.0/index.html                                    | 2 +-
 content/docs/12.3.0/searchindex.js                                | 2 +-
 .../latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt | 2 +-
 .../docs/latest/_sources/components/net/wqueuedeadlocks.rst.txt   | 2 +-
 content/docs/latest/_sources/components/nxgraphics/nx.rst.txt     | 2 +-
 content/docs/latest/_sources/guides/citests.rst.txt               | 2 +-
 content/docs/latest/_sources/guides/stm32ccm.rst.txt              | 2 +-
 content/docs/latest/_sources/guides/testingtcpip.rst.txt          | 4 ++--
 .../docs/latest/_sources/implementation/critical_sections.rst.txt | 6 +++---
 .../latest/_sources/implementation/processes_vs_tasks.rst.txt     | 2 +-
 .../platforms/arm/stm32h7/boards/linum-stm32h753bi/index.rst.txt  | 6 +++---
 content/docs/latest/applications/graphics/nxwm/cnxconsole.html    | 2 +-
 content/docs/latest/components/net/wqueuedeadlocks.html           | 2 +-
 content/docs/latest/components/nxgraphics/nx.html                 | 2 +-
 content/docs/latest/guides/citests.html                           | 2 +-
 content/docs/latest/guides/stm32ccm.html                          | 2 +-
 content/docs/latest/guides/testingtcpip.html                      | 4 ++--
 content/docs/latest/implementation/critical_sections.html         | 6 +++---
 content/docs/latest/implementation/processes_vs_tasks.html        | 2 +-
 content/docs/latest/index.html                                    | 2 +-
 .../platforms/arm/lpc17xx/boards/olimex-lpc1766stk/index.html     | 2 +-
 .../platforms/arm/stm32h7/boards/linum-stm32h753bi/index.html     | 6 +++---
 .../docs/latest/platforms/mips/pic32mx/boards/mirtoo/index.html   | 2 +-
 .../latest/platforms/risc-v/rv32m1/boards/rv32m1-vega/index.html  | 8 ++++----
 content/docs/latest/searchindex.js                                | 2 +-
 content/feed.xml                                                  | 4 ++--
 48 files changed, 62 insertions(+), 62 deletions(-)

diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index ee696ba7..fb0be64a 100644
--- a/content/docs/10.0.0/index.html
+++ b/content/docs/10.0.0/index.html
@@ -131,7 +131,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller environments, the primary governing standards in NuttX are Posix and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:09</p>
+<p>Last Updated: 25 November 23 at 00:09</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.0.0/searchindex.js b/content/docs/10.0.0/searchindex.js
index 0fbb6bb3..ed1634fe 100644
--- a/content/docs/10.0.0/searchindex.js
+++ b/content/docs/10.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
diff --git a/content/docs/10.0.1/index.html b/content/docs/10.0.1/index.html
index 4025734f..4ac15aec 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller environments, the primary governing standards in NuttX are Posix and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:09</p>
+<p>Last Updated: 25 November 23 at 00:09</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.0.1/searchindex.js b/content/docs/10.0.1/searchindex.js
index c8037aff..b26aebcc 100644
--- a/content/docs/10.0.1/searchindex.js
+++ b/content/docs/10.0.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "boards/index", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/index", "components/drivers/character/keypad", "components/drivers/character/pwm", "components/drivers/character/quadrature", "components/drivers/character/rtc", "components/drivers/character/serial", "components/drivers/character/timer", "components/drivers/chara [...]
\ No newline at end of file
diff --git a/content/docs/10.1.0/index.html b/content/docs/10.1.0/index.html
index 6111f31b..03f2732a 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -152,7 +152,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:09</p>
+<p>Last Updated: 25 November 23 at 00:09</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.1.0/searchindex.js b/content/docs/10.1.0/searchindex.js
index beb4614f..032d1c8e 100644
--- a/content/docs/10.1.0/searchindex.js
+++ b/content/docs/10.1.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/10.2.0/index.html b/content/docs/10.2.0/index.html
index b44fc3f5..f3f9afc0 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:10</p>
+<p>Last Updated: 25 November 23 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.2.0/searchindex.js b/content/docs/10.2.0/searchindex.js
index 7242ef15..dc53dd97 100644
--- a/content/docs/10.2.0/searchindex.js
+++ b/content/docs/10.2.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/10.3.0/index.html b/content/docs/10.3.0/index.html
index b44fc3f5..f3f9afc0 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:10</p>
+<p>Last Updated: 25 November 23 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/10.3.0/searchindex.js b/content/docs/10.3.0/searchindex.js
index cc275f87..dca2c977 100644
--- a/content/docs/10.3.0/searchindex.js
+++ b/content/docs/10.3.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/11.0.0/index.html b/content/docs/11.0.0/index.html
index b44fc3f5..f3f9afc0 100644
--- a/content/docs/11.0.0/index.html
+++ b/content/docs/11.0.0/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:10</p>
+<p>Last Updated: 25 November 23 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/11.0.0/searchindex.js b/content/docs/11.0.0/searchindex.js
index 2f3f3886..3c0dedfb 100644
--- a/content/docs/11.0.0/searchindex.js
+++ b/content/docs/11.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/12.0.0/index.html b/content/docs/12.0.0/index.html
index c526ada1..a8dcfa68 100644
--- a/content/docs/12.0.0/index.html
+++ b/content/docs/12.0.0/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:10</p>
+<p>Last Updated: 25 November 23 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.0.0/searchindex.js b/content/docs/12.0.0/searchindex.js
index a718383e..8f85971c 100644
--- a/content/docs/12.0.0/searchindex.js
+++ b/content/docs/12.0.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/12.1.0/index.html b/content/docs/12.1.0/index.html
index a04312c4..8408f68f 100644
--- a/content/docs/12.1.0/index.html
+++ b/content/docs/12.1.0/index.html
@@ -153,7 +153,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:10</p>
+<p>Last Updated: 25 November 23 at 00:10</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.1.0/searchindex.js b/content/docs/12.1.0/searchindex.js
index e8070a58..0ee03c34 100644
--- a/content/docs/12.1.0/searchindex.js
+++ b/content/docs/12.1.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "components/binfmt", "components/drivers/block/index", "components/drivers/character/analog", "components/drivers/character/can", "components/drivers/character/foc", "components/drivers/character/index", "components [...]
\ No newline at end of file
diff --git a/content/docs/12.2.0/index.html b/content/docs/12.2.0/index.html
index b5029462..2224a058 100644
--- a/content/docs/12.2.0/index.html
+++ b/content/docs/12.2.0/index.html
@@ -156,7 +156,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:11</p>
+<p>Last Updated: 25 November 23 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.2.0/searchindex.js b/content/docs/12.2.0/searchindex.js
index bd2a7c0b..6a8fa5d8 100644
--- a/content/docs/12.2.0/searchindex.js
+++ b/content/docs/12.2.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.2.1/index.html b/content/docs/12.2.1/index.html
index b5029462..2224a058 100644
--- a/content/docs/12.2.1/index.html
+++ b/content/docs/12.2.1/index.html
@@ -156,7 +156,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:11</p>
+<p>Last Updated: 25 November 23 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html b/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
index d3afe00a..22562500 100644
--- a/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
+++ b/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-audio-kit/index.html
@@ -337,7 +337,7 @@ Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/)
 <p>Look for your PC IP address and test playing the prepared audio on your
 browser:</p>
 <figure class="align-center">
-<img alt="../../../../../_images/esp32-audio-config-file.png" src="../../../../../_images/esp32-audio-config-file.png" />
+<img alt="../../../../../_images/esp32-audio-config-file1.png" src="../../../../../_images/esp32-audio-config-file1.png" />
 </figure>
 <p>After successfully built and flashed, connect the board to the Wi-Fi network:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ nsh&gt; wapi psk wlan0 mypasswd 3
diff --git a/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-devkitc/index.html b/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
index 7fad96f2..7674e958 100644
--- a/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
+++ b/content/docs/12.2.1/platforms/xtensa/esp32/boards/esp32-devkitc/index.html
@@ -434,7 +434,7 @@ Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/)
 <p>Look for your PC IP address and test playing the prepared audio on your
 browser:</p>
 <figure class="align-center">
-<img alt="../../../../../_images/esp32-audio-config-file1.png" src="../../../../../_images/esp32-audio-config-file1.png" />
+<img alt="../../../../../_images/esp32-audio-config-file.png" src="../../../../../_images/esp32-audio-config-file.png" />
 </figure>
 <p>After successfully built and flashed, connect the board to the Wi-Fi network:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>nsh&gt; wapi psk wlan0 mypasswd 3
diff --git a/content/docs/12.2.1/searchindex.js b/content/docs/12.2.1/searchindex.js
index e577df37..f614a40c 100644
--- a/content/docs/12.2.1/searchindex.js
+++ b/content/docs/12.2.1/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/12.3.0/index.html b/content/docs/12.3.0/index.html
index 4c88bf1f..b63956f0 100644
--- a/content/docs/12.3.0/index.html
+++ b/content/docs/12.3.0/index.html
@@ -156,7 +156,7 @@ by following these <a class="reference internal" href="contributing/documentatio
 <section id="nuttx-documentation">
 <h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation" title="Permalink to this heading"></a></h1>
 <p>NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOS’s (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:11</p>
+<p>Last Updated: 25 November 23 at 00:11</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/12.3.0/searchindex.js b/content/docs/12.3.0/searchindex.js
index 3abdd038..332b2d60 100644
--- a/content/docs/12.3.0/searchindex.js
+++ b/content/docs/12.3.0/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/index", "applications/nsh/builtin", "applications/nsh/commands", "applications/nsh/config", "applications/nsh/customizing", "applications/nsh/index", "applications/nsh/installation", "applications/nsh/login", "applications/nsh/nsh", "applications/nxdiag/config", "applications/nxdiag/index", "applications/wapi/commands", "applications/wapi/index", "applications/wapi/wireless", "components/binfmt", "components/drivers/block/index", "components/dr [...]
\ No newline at end of file
diff --git a/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt b/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
index b3ce36f1..e96d2fb2 100644
--- a/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
+++ b/content/docs/latest/_sources/applications/graphics/nxwm/cnxconsole.rst.txt
@@ -127,7 +127,7 @@ pretty good description of how mouse/touchscreen input works.
 
 The mouse/touchscreen input is a little simpler, however: The main simplication
 is that the additional complexities of the NxConsole and its special input device
-do not apply. Mouse/touchscreen inut as always steered to widgets when the
+do not apply. Mouse/touchscreen input as always steered to widgets when the
 callback is received in ``CCallback::newMouseEvent`` by an unconditional call to
 ``CWidgetControl::newMouseEvent``. There is a "fork in the road" at the
 corresponding point in the logic of ``CCallback::newKeyboardEvent``
diff --git a/content/docs/latest/_sources/components/net/wqueuedeadlocks.rst.txt b/content/docs/latest/_sources/components/net/wqueuedeadlocks.rst.txt
index 4f274d3d..a2c35aeb 100644
--- a/content/docs/latest/_sources/components/net/wqueuedeadlocks.rst.txt
+++ b/content/docs/latest/_sources/components/net/wqueuedeadlocks.rst.txt
@@ -100,7 +100,7 @@ of a ``send()`` or ``sendto()`` transfer, then the operation will block until IO
 available if ``O_NONBLOCK`` is not selected. This delay can can be a substantial amount
 of time.
 
-Second, if ``O_NONBLOCK`` is selected, the send will, of course, return immediatly,
+Second, if ``O_NONBLOCK`` is selected, the send will, of course, return immediately,
 failing with errno set ``EAGAIN`` if we cannot allocate the first IOB for the transfer.
 
 The third behavior occurs if the we run out of IOBs in the middle of the transfer.
diff --git a/content/docs/latest/_sources/components/nxgraphics/nx.rst.txt b/content/docs/latest/_sources/components/nxgraphics/nx.rst.txt
index 899ebc57..b44bdacc 100644
--- a/content/docs/latest/_sources/components/nxgraphics/nx.rst.txt
+++ b/content/docs/latest/_sources/components/nxgraphics/nx.rst.txt
@@ -29,7 +29,7 @@ features:
 * **Device Interface** NX supports any graphics device either of two
   device interfaces:
 
-  #. Any device with random accesss video memory using the NuttX framebuffer
+  #. Any device with random access video memory using the NuttX framebuffer
      driver interface (see include/nuttx/video/fb.h).
   #. Any LCD-like device than can accept raster line runs through a parallel
      or serial interface (see include/nuttx/lcd/lcd.h). By default, NX is
diff --git a/content/docs/latest/_sources/guides/citests.rst.txt b/content/docs/latest/_sources/guides/citests.rst.txt
index e3be2241..cb2b0aee 100644
--- a/content/docs/latest/_sources/guides/citests.rst.txt
+++ b/content/docs/latest/_sources/guides/citests.rst.txt
@@ -7,7 +7,7 @@ Running CI Test Locally
 
 NuttX automatically runs continuous integration (CI) tests on 
 `simulator <https://nuttx.apache.org/docs/latest/guides/simulator.html>`__
-target when new pull request is submited. To avoid the tests failing you can
+target when new pull request is submitted. To avoid the tests failing you can
 also run them locally on your computer prior to submiting new pull request.
 This page describes the step by step manual to do so.
 
diff --git a/content/docs/latest/_sources/guides/stm32ccm.rst.txt b/content/docs/latest/_sources/guides/stm32ccm.rst.txt
index 16ce123f..cc0cb257 100644
--- a/content/docs/latest/_sources/guides/stm32ccm.rst.txt
+++ b/content/docs/latest/_sources/guides/stm32ccm.rst.txt
@@ -40,7 +40,7 @@ NOTE: These interfaces are, technically, not prototyped since they are really
 provided via C pre-processor macros.
 
 NOTE: In order to use the CCM memory allocator functions, you must first call
-``ccm_initialize()`` somwhere in your early boot-up logic.
+``ccm_initialize()`` somewhere in your early boot-up logic.
 
 With these interfaces you have a (nearly) standard way to manage memory from a
 heap that consists of the the CCM SRAM. And, since the CCM memory is no longer
diff --git a/content/docs/latest/_sources/guides/testingtcpip.rst.txt b/content/docs/latest/_sources/guides/testingtcpip.rst.txt
index fba25b8e..4e07ecc5 100644
--- a/content/docs/latest/_sources/guides/testingtcpip.rst.txt
+++ b/content/docs/latest/_sources/guides/testingtcpip.rst.txt
@@ -127,8 +127,8 @@ on these requests a application specific fuzz test can be generated.
    # Record requests to the target at 192.168.2.135 on port 80
    ~/SPIKE/src/requests$ ../webmitm -t 192.168.2.135 -p 80
 
-Now use your web applicaiton through localhost to record some requests. Then you
-can generate your application specific fuzz test from the recorded requests.
+Now use your web application through localhost to record some requests. Then you
+can generate your application-specific fuzz test from the recorded requests.
 
 .. code-block:: bash
 
diff --git a/content/docs/latest/_sources/implementation/critical_sections.rst.txt b/content/docs/latest/_sources/implementation/critical_sections.rst.txt
index 80493250..c5fcd31f 100644
--- a/content/docs/latest/_sources/implementation/critical_sections.rst.txt
+++ b/content/docs/latest/_sources/implementation/critical_sections.rst.txt
@@ -43,7 +43,7 @@ OS Interfaces
 -------------
 
 Before we talk about SMP Critical Sections let's first review the internal OS
-interfaces avaiable and what they do in the single CPU case:
+interfaces available and what they do in the single CPU case:
 
 * ``up_irq_save()`` (and its companion, ``up_irq_restore()``). These simple
   interfaces just enable and disable interrupts globally. This is the simplest
@@ -272,7 +272,7 @@ This file cat be read from NSH like:
    nsh> cat /proc/1/critmon
    0.000009610,0.000001165
 
-The form of the output from the ``/proc/critmon`` file is simlar::
+The form of the output from the ``/proc/critmon`` file is similar::
 
   X,X.XXXXXXXXX,X.XXXXXXXXX
 
@@ -295,7 +295,7 @@ file was read.
 ``apps/system/critmon``
 -----------------------
 
-Also available is a application daemon at ``apps/sysem/critmon``. This daemon
+Also available is a application daemon at ``apps/system/critmon``. This daemon
 periodically reads the ProcFS files described above and dumps the output to
 stdout. This daemon is enabled with:
 
diff --git a/content/docs/latest/_sources/implementation/processes_vs_tasks.rst.txt b/content/docs/latest/_sources/implementation/processes_vs_tasks.rst.txt
index 16626a58..c30a42d9 100644
--- a/content/docs/latest/_sources/implementation/processes_vs_tasks.rst.txt
+++ b/content/docs/latest/_sources/implementation/processes_vs_tasks.rst.txt
@@ -12,7 +12,7 @@ NuttX Build Types
 
 NuttX can be built in several different ways:
 
-* **Kernel Build** The kernal build, selected with ``CONFIG_BUILD_KERNEL``, uses
+* **Kernel Build** The kernel build, selected with ``CONFIG_BUILD_KERNEL``, uses
   the MCU's Memory Management Unit (MMU) to implement processes very similar to
   Linux processes. There is no interesting discussion here; NuttX behaves very
   much like Linux.
diff --git a/content/docs/latest/_sources/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.rst.txt b/content/docs/latest/_sources/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.rst.txt
index bcb8fe97..98ddd7dd 100644
--- a/content/docs/latest/_sources/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.rst.txt
@@ -25,7 +25,7 @@ The board features:
 - Crystal for RTC 32.768KHz
 - 1 UART serial for debug
 - 1 Led RGB
-- 1 Buzzer without internal oscilator
+- 1 Buzzer without internal oscillator
 - 1 Mono audio up to 3W
 - 1 Ethernet 10/100
 - 1 MicroSD connector supporting 1 or 4-bit bus
@@ -300,7 +300,7 @@ The LINUM-STM32H753BI has a external SDRAM with 16Mbits connected to FMC periphe
 
 LCD
 =======
-The LINUM-STM32H753BI use the LTDC to suport one LCD with RGB connection.
+The LINUM-STM32H753BI use the LTDC to support one LCD with RGB connection.
 
   =========== =====
   LTDC        PINS
@@ -354,7 +354,7 @@ The LINUM-STM32H753BI has one I2S output.
 
 BUZZER
 =======
-The LINUM-STM32H753BI has a buzzer without internal oscilator
+The LINUM-STM32H753BI has a buzzer without internal oscillator
 
   ======= =====
   GPIO    PINS
diff --git a/content/docs/latest/applications/graphics/nxwm/cnxconsole.html b/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
index f7f5ae2c..2ad0a9e5 100644
--- a/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
+++ b/content/docs/latest/applications/graphics/nxwm/cnxconsole.html
@@ -315,7 +315,7 @@ were to replace the names keyboard to mouse, kbdin to mousein, etc. you have a
 pretty good description of how mouse/touchscreen input works.</p>
 <p>The mouse/touchscreen input is a little simpler, however: The main simplication
 is that the additional complexities of the NxConsole and its special input device
-do not apply. Mouse/touchscreen inut as always steered to widgets when the
+do not apply. Mouse/touchscreen input as always steered to widgets when the
 callback is received in <code class="docutils literal notranslate"><span class="pre">CCallback::newMouseEvent</span></code> by an unconditional call to
 <code class="docutils literal notranslate"><span class="pre">CWidgetControl::newMouseEvent</span></code>. There is a “fork in the road” at the
 corresponding point in the logic of <code class="docutils literal notranslate"><span class="pre">CCallback::newKeyboardEvent</span></code></p>
diff --git a/content/docs/latest/components/net/wqueuedeadlocks.html b/content/docs/latest/components/net/wqueuedeadlocks.html
index 682046fa..e143a23b 100644
--- a/content/docs/latest/components/net/wqueuedeadlocks.html
+++ b/content/docs/latest/components/net/wqueuedeadlocks.html
@@ -270,7 +270,7 @@ IOB pool has been exhausted: First, if there are no available IOBs at the beginn
 of a <code class="docutils literal notranslate"><span class="pre">send()</span></code> or <code class="docutils literal notranslate"><span class="pre">sendto()</span></code> transfer, then the operation will block until IOBs are again
 available if <code class="docutils literal notranslate"><span class="pre">O_NONBLOCK</span></code> is not selected. This delay can can be a substantial amount
 of time.</p>
-<p>Second, if <code class="docutils literal notranslate"><span class="pre">O_NONBLOCK</span></code> is selected, the send will, of course, return immediatly,
+<p>Second, if <code class="docutils literal notranslate"><span class="pre">O_NONBLOCK</span></code> is selected, the send will, of course, return immediately,
 failing with errno set <code class="docutils literal notranslate"><span class="pre">EAGAIN</span></code> if we cannot allocate the first IOB for the transfer.</p>
 <p>The third behavior occurs if the we run out of IOBs in the middle of the transfer.
 Then the send operation will not wait but will instead send then number of bytes that
diff --git a/content/docs/latest/components/nxgraphics/nx.html b/content/docs/latest/components/nxgraphics/nx.html
index bb2ac361..dd379f3d 100644
--- a/content/docs/latest/components/nxgraphics/nx.html
+++ b/content/docs/latest/components/nxgraphics/nx.html
@@ -212,7 +212,7 @@ only a primitive set of graphic and rendering operations.</p></li>
 <li><p><strong>Device Interface</strong> NX supports any graphics device either of two
 device interfaces:</p>
 <ol class="arabic simple">
-<li><p>Any device with random accesss video memory using the NuttX framebuffer
+<li><p>Any device with random access video memory using the NuttX framebuffer
 driver interface (see include/nuttx/video/fb.h).</p></li>
 <li><p>Any LCD-like device than can accept raster line runs through a parallel
 or serial interface (see include/nuttx/lcd/lcd.h). By default, NX is
diff --git a/content/docs/latest/guides/citests.html b/content/docs/latest/guides/citests.html
index 655f3f1c..ad9a1108 100644
--- a/content/docs/latest/guides/citests.html
+++ b/content/docs/latest/guides/citests.html
@@ -178,7 +178,7 @@
 <span id="citests"></span><h1>Running CI Test Locally<a class="headerlink" href="#running-ci-test-locally" title="Permalink to this heading"></a></h1>
 <p>NuttX automatically runs continuous integration (CI) tests on
 <a class="reference external" href="https://nuttx.apache.org/docs/latest/guides/simulator.html">simulator</a>
-target when new pull request is submited. To avoid the tests failing you can
+target when new pull request is submitted. To avoid the tests failing you can
 also run them locally on your computer prior to submiting new pull request.
 This page describes the step by step manual to do so.</p>
 <section id="configuring-nuttx">
diff --git a/content/docs/latest/guides/stm32ccm.html b/content/docs/latest/guides/stm32ccm.html
index 16ee5c93..59c18b37 100644
--- a/content/docs/latest/guides/stm32ccm.html
+++ b/content/docs/latest/guides/stm32ccm.html
@@ -210,7 +210,7 @@ interfaces prototyped in the <code class="docutils literal notranslate"><span cl
 <p>NOTE: These interfaces are, technically, not prototyped since they are really
 provided via C pre-processor macros.</p>
 <p>NOTE: In order to use the CCM memory allocator functions, you must first call
-<code class="docutils literal notranslate"><span class="pre">ccm_initialize()</span></code> somwhere in your early boot-up logic.</p>
+<code class="docutils literal notranslate"><span class="pre">ccm_initialize()</span></code> somewhere in your early boot-up logic.</p>
 <p>With these interfaces you have a (nearly) standard way to manage memory from a
 heap that consists of the the CCM SRAM. And, since the CCM memory is no longer
 a part of the normal heap, all allocated I/O buffers will be DMA-able (unless you
diff --git a/content/docs/latest/guides/testingtcpip.html b/content/docs/latest/guides/testingtcpip.html
index 6286d84b..2a25bc39 100644
--- a/content/docs/latest/guides/testingtcpip.html
+++ b/content/docs/latest/guides/testingtcpip.html
@@ -279,8 +279,8 @@ on these requests a application specific fuzz test can be generated.</p>
 ~/SPIKE/src/requests$<span class="w"> </span>../webmitm<span class="w"> </span>-t<span class="w"> </span><span class="m">192</span>.168.2.135<span class="w"> </span>-p<span class="w"> </span><span class="m">80</span>
 </pre></div>
 </div>
-<p>Now use your web applicaiton through localhost to record some requests. Then you
-can generate your application specific fuzz test from the recorded requests.</p>
+<p>Now use your web application through localhost to record some requests. Then you
+can generate your application-specific fuzz test from the recorded requests.</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>~/SPIKE/src$<span class="w"> </span>./makewebfuzz.pl<span class="w"> </span>./requests/http_request-1.0<span class="w"> </span>&gt;<span class="w"> </span>myfuzz.c
 ~/SPIKE/src$<span class="w"> </span>gcc<span class="w"> </span>./myfuzz.c<span class="w"> </span>-I../include<span class="w"> </span>-o<span class="w"> </span>myfuzz<span class="w"> </span>-L.<span class="w"> </span>-ldlrpc<span class="w"> </span>-ldl
 </pre></div>
diff --git a/content/docs/latest/implementation/critical_sections.html b/content/docs/latest/implementation/critical_sections.html
index c5775049..b4b4356d 100644
--- a/content/docs/latest/implementation/critical_sections.html
+++ b/content/docs/latest/implementation/critical_sections.html
@@ -214,7 +214,7 @@ interrupts.</p>
 <section id="os-interfaces">
 <h3>OS Interfaces<a class="headerlink" href="#os-interfaces" title="Permalink to this heading"></a></h3>
 <p>Before we talk about SMP Critical Sections let’s first review the internal OS
-interfaces avaiable and what they do in the single CPU case:</p>
+interfaces available and what they do in the single CPU case:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">up_irq_save()</span></code> (and its companion, <code class="docutils literal notranslate"><span class="pre">up_irq_restore()</span></code>). These simple
 interfaces just enable and disable interrupts globally. This is the simplest
@@ -408,7 +408,7 @@ section was held.</p>
 <span class="m">0</span>.000009610,0.000001165
 </pre></div>
 </div>
-<p>The form of the output from the <code class="docutils literal notranslate"><span class="pre">/proc/critmon</span></code> file is simlar:</p>
+<p>The form of the output from the <code class="docutils literal notranslate"><span class="pre">/proc/critmon</span></code> file is similar:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>X,X.XXXXXXXXX,X.XXXXXXXXX
 </pre></div>
 </div>
@@ -427,7 +427,7 @@ file was read.</p>
 </section>
 <section id="apps-system-critmon">
 <h3><code class="docutils literal notranslate"><span class="pre">apps/system/critmon</span></code><a class="headerlink" href="#apps-system-critmon" title="Permalink to this heading"></a></h3>
-<p>Also available is a application daemon at <code class="docutils literal notranslate"><span class="pre">apps/sysem/critmon</span></code>. This daemon
+<p>Also available is a application daemon at <code class="docutils literal notranslate"><span class="pre">apps/system/critmon</span></code>. This daemon
 periodically reads the ProcFS files described above and dumps the output to
 stdout. This daemon is enabled with:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>nsh&gt;<span class="w"> </span>critmon_start
diff --git a/content/docs/latest/implementation/processes_vs_tasks.html b/content/docs/latest/implementation/processes_vs_tasks.html
index 26013d42..9767098d 100644
--- a/content/docs/latest/implementation/processes_vs_tasks.html
+++ b/content/docs/latest/implementation/processes_vs_tasks.html
@@ -179,7 +179,7 @@ those differences.</p>
 <h2>NuttX Build Types<a class="headerlink" href="#nuttx-build-types" title="Permalink to this heading"></a></h2>
 <p>NuttX can be built in several different ways:</p>
 <ul class="simple">
-<li><p><strong>Kernel Build</strong> The kernal build, selected with <code class="docutils literal notranslate"><span class="pre">CONFIG_BUILD_KERNEL</span></code>, uses
+<li><p><strong>Kernel Build</strong> The kernel build, selected with <code class="docutils literal notranslate"><span class="pre">CONFIG_BUILD_KERNEL</span></code>, uses
 the MCU’s Memory Management Unit (MMU) to implement processes very similar to
 Linux processes. There is no interesting discussion here; NuttX behaves very
 much like Linux.</p></li>
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index a966b564..62887bdb 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -163,7 +163,7 @@ standards. Additional standard APIs from Unix and other common RTOS’s (such as
 VxWorks) are adopted for functionality not available under these standards, or
 for functionality that is not appropriate for deeply-embedded environments (such
 as fork()).</p>
-<p>Last Updated: 24 November 23 at 00:12</p>
+<p>Last Updated: 25 November 23 at 00:12</p>
 <div class="toctree-wrapper compound">
 <p class="caption" role="heading"><span class="caption-text">Table of Contents</span></p>
 <ul class="current">
diff --git a/content/docs/latest/platforms/arm/lpc17xx/boards/olimex-lpc1766stk/index.html b/content/docs/latest/platforms/arm/lpc17xx/boards/olimex-lpc1766stk/index.html
index 77eead29..7855aa90 100644
--- a/content/docs/latest/platforms/arm/lpc17xx/boards/olimex-lpc1766stk/index.html
+++ b/content/docs/latest/platforms/arm/lpc17xx/boards/olimex-lpc1766stk/index.html
@@ -363,7 +363,7 @@ Olimex LPC1766-STK development board
   The LPC1766-STK has a Nokia 6100 132x132 LCD and either a Phillips PCF8833
   or an Epson S1D15G10 LCD controller.  The NuttX configuration may have to
   be adjusted depending on which controller is used with the LCD.  The
-  &quot;LPC1766-STK development board Users Manual&quot; states tha the board features
+  &quot;LPC1766-STK development board Users Manual&quot; states that the board features
   a &quot;LCD NOKIA 6610 128x128 x12bit color TFT with Epson LCD controller.&quot;
   But, referring to a different Olimex board, &quot;Nokia 6100 LCD Display
   Driver,&quot; Revision 1, James P. Lynch (&quot;Nokia 6100 LCD Display Driver.pdf&quot;)
diff --git a/content/docs/latest/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.html b/content/docs/latest/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.html
index cb6fcdbd..d1e0e417 100644
--- a/content/docs/latest/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.html
+++ b/content/docs/latest/platforms/arm/stm32h7/boards/linum-stm32h753bi/index.html
@@ -265,7 +265,7 @@ touchscreen and another for access to other peripherals of microcontroller.</p>
 - Crystal for RTC 32.768KHz
 - 1 UART serial for debug
 - 1 Led RGB
-- 1 Buzzer without internal oscilator
+- 1 Buzzer without internal oscillator
 - 1 Mono audio up to 3W
 - 1 Ethernet 10/100
 - 1 MicroSD connector supporting 1 or 4-bit bus
@@ -779,7 +779,7 @@ The NOR memory used is the W25Q128JV with 16MB</p>
 </section>
 <section id="lcd">
 <h2>LCD<a class="headerlink" href="#lcd" title="Permalink to this heading"></a></h2>
-<p>The LINUM-STM32H753BI use the LTDC to suport one LCD with RGB connection.</p>
+<p>The LINUM-STM32H753BI use the LTDC to support one LCD with RGB connection.</p>
 <blockquote>
 <div><table class="docutils align-default">
 <thead>
@@ -903,7 +903,7 @@ The NOR memory used is the W25Q128JV with 16MB</p>
 </section>
 <section id="buzzer">
 <h2>BUZZER<a class="headerlink" href="#buzzer" title="Permalink to this heading"></a></h2>
-<p>The LINUM-STM32H753BI has a buzzer without internal oscilator</p>
+<p>The LINUM-STM32H753BI has a buzzer without internal oscillator</p>
 <blockquote>
 <div><table class="docutils align-default">
 <thead>
diff --git a/content/docs/latest/platforms/mips/pic32mx/boards/mirtoo/index.html b/content/docs/latest/platforms/mips/pic32mx/boards/mirtoo/index.html
index 614459fd..40b9224d 100644
--- a/content/docs/latest/platforms/mips/pic32mx/boards/mirtoo/index.html
+++ b/content/docs/latest/platforms/mips/pic32mx/boards/mirtoo/index.html
@@ -607,7 +607,7 @@ Toolchains
 
   Even then, there are more warnings from the linker and some undefined symbols
   for non-NuttX code that resides in the unused Microchip libraries.  You will
-  have to solve at least this undefined symbol problem if you want to used thei
+  have to solve at least this undefined symbol problem if you want to use their
   XC32 toolchain.
 
   Windows Native Toolchains
diff --git a/content/docs/latest/platforms/risc-v/rv32m1/boards/rv32m1-vega/index.html b/content/docs/latest/platforms/risc-v/rv32m1/boards/rv32m1-vega/index.html
index 99358746..a860c37a 100644
--- a/content/docs/latest/platforms/risc-v/rv32m1/boards/rv32m1-vega/index.html
+++ b/content/docs/latest/platforms/risc-v/rv32m1/boards/rv32m1-vega/index.html
@@ -213,7 +213,7 @@ Refer to https://open-isa.org for further information about this board.
 Currently NuttX is ported to RV32M1 RI5CY only. RI5CY is RV32IMC RISC-V CPU
 with PULP extensions features:
   - Post-Incrementing load and stores,
-  - Multiply-Accumulate extenstions,
+  - Multiply-Accumulate extensions,
   - ALU extensions,
   - Hardware Loops.
 
@@ -268,7 +268,7 @@ Default LPUART Configuration
 
 LPUART0 is enabled in most configurations (see */defconfig). RX and TX are
 configured on pins PC7 and PC8, respectively (see include/board.h). These
-two above pins are connected to onboard Debug Adpater which provides a USB-
+two above pins are connected to onboard Debug Adapter which provides a USB-
 TTL serial channel.
 
 Buttons
@@ -354,9 +354,9 @@ Program
 To program RV32M1, openocd from OPEN ISA and an external jtag adapter are pre-
 requisite. There are 2 tested jtag adapters: Segger Jlink EDU mini and SiPEED
 USB Jtag Adapter. The Segger Jlink EDU mini can connect J55 header on RV32M1-VEGA
-board directly while SiPEED USB Jtag Adpater has to co-operate with an Adapter
+board directly while SiPEED USB Jtag Adapter has to co-operate with an Adapter
 board to setup wires connection.
-Compared to Segger Jlink EDU Mini Adapter, SiPEED USB Jtag Adpater is cheaper but
+Compared to Segger Jlink EDU Mini Adapter, SiPEED USB Jtag Adapter is cheaper but
 not inferior.
 
 With SiPEED USB Jtag Adapter, some patches must be applied to rv32m1_ri5cy.cfg:
diff --git a/content/docs/latest/searchindex.js b/content/docs/latest/searchindex.js
index 1da3712d..56331620 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["applications/audioutils/fmsynt/index", "applications/audioutils/index", "applications/audioutils/mml_parser/index", "applications/audioutils/nxaudio/index", "applications/benchmarks/coremark/index", "applications/benchmarks/index", "applications/boot/index", "applications/boot/mcuboot/index", "applications/boot/miniboot/index", "applications/canutils/candump/index", "applications/canutils/canlib/index", "applications/canutils/cansend/index", "applications/c [...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index e60026a5..756346c9 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
     <description></description>
     <link>/</link>
     <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Fri, 24 Nov 2023 00:12:59 +0000</pubDate>
-    <lastBuildDate>Fri, 24 Nov 2023 00:12:59 +0000</lastBuildDate>
+    <pubDate>Sat, 25 Nov 2023 00:13:16 +0000</pubDate>
+    <lastBuildDate>Sat, 25 Nov 2023 00:13:16 +0000</lastBuildDate>
     <generator>Jekyll v4.3.2</generator>
     
       <item>