summaryrefslogtreecommitdiffstatshomepage
path: root/docs/reference
diff options
context:
space:
mode:
authorchuangjinglu <chuangjinglu@outlook.com>2024-11-25 11:06:15 +0800
committerDamien George <damien@micropython.org>2024-11-30 13:08:33 +1100
commit2e796d6c3e33e2d3b1936cd05aa926400ad1d5b7 (patch)
treed8da1231caa87036fe1724640efa1efb2e74538b /docs/reference
parent3de3821abf7e245566be227c9799b74d6b80aae3 (diff)
downloadmicropython-2e796d6c3e33e2d3b1936cd05aa926400ad1d5b7.tar.gz
micropython-2e796d6c3e33e2d3b1936cd05aa926400ad1d5b7.zip
docs,ports: Fix some comments and error messages with doubled-up words.
Signed-off-by: chuangjinglu <chuangjinglu@outlook.com>
Diffstat (limited to 'docs/reference')
-rw-r--r--docs/reference/manifest.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reference/manifest.rst b/docs/reference/manifest.rst
index 1a80b1259e..dc9d6dd75b 100644
--- a/docs/reference/manifest.rst
+++ b/docs/reference/manifest.rst
@@ -26,7 +26,7 @@ re-flashing the entire firmware. However, it can still be useful to
selectively freeze some rarely-changing dependencies (such as third-party
libraries).
-The way to list the Python files to be be frozen into the firmware is via
+The way to list the Python files to be frozen into the firmware is via
a "manifest", which is a Python file that will be interpreted by the build
process. Typically you would write a manifest file as part of a board
definition, but you can also write a stand-alone manifest file and use it with