summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorVivien Didelot <vdidelot@pbsc.com>2021-04-06 11:01:20 -0400
committerSascha Hauer <s.hauer@pengutronix.de>2021-04-13 08:13:09 +0200
commitb9636c16cb710cd11985a12ed33b985a1324a6b7 (patch)
tree9e0465df0896fe2af6eae0d17b57cca9e405caad /Documentation
parent45804d9208d786f3efe60403761a13e308d0b989 (diff)
downloadbarebox-b9636c16cb710cd11985a12ed33b985a1324a6b7.tar.gz
barebox-b9636c16cb710cd11985a12ed33b985a1324a6b7.tar.xz
Documentation: fix sucessfuly -> successfully typo
system-reset.rst was embedded a classic sucess -> success typo. Fix it. Signed-off-by: Vivien Didelot <vdidelot@pbsc.com> Link: https://lore.pengutronix.de/20210406150120.4194149-1-vivien.didelot@gmail.com Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/user/system-reset.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/user/system-reset.rst b/Documentation/user/system-reset.rst
index e76e3a23c1..bf7369d06f 100644
--- a/Documentation/user/system-reset.rst
+++ b/Documentation/user/system-reset.rst
@@ -31,7 +31,7 @@ But there are some drawbacks within this simple approach.
* some SoC's boot behaviour gets parametrized by so called 'bootstrap pins'.
These pins can have a different meaning at reset time and at run-time later
on (multi purpose pins) but their correct values at reset time are very
- important to boot the SoC sucessfully. If external devices are connected to
+ important to boot the SoC successfully. If external devices are connected to
these multi purpose pins they can disturb the reset values, and so parametrizing
the boot behaviour differently and hence crashing the SoC until the next real
POR happens which also resets the external devices (and keep them away from the