As reported on ecos-discuss
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
Index: packages/redboot/current/doc/redboot_cmds.sgml
===================================================================
RCS file: /misc/cvsfiles/ecos/packages/redboot/current/doc/redboot_cmds.sgml,v
retrieving revision 1.15
diff -u -5 -p -r1.15 redboot_cmds.sgml
--- packages/redboot/current/doc/redboot_cmds.sgml 20 Jul 2006 20:27:47
-0000 1.15
+++ packages/redboot/current/doc/redboot_cmds.sgml 15 Dec 2006 12:24:20
-0000
@@ -2272,11 +2272,11 @@ RedBoot> <userinput>fis free</userinput>
operation, it must be specified.</entry>
</row>
<row>
<entry>-l</entry>
<entry>Number</entry>
- <entry>Length of flash area to occopy. If specified, and
+ <entry>Length of flash area to occupy. If specified, and
the named image already exists, the length must match
the value in the FIS directory.</entry>
<entry>Length of area reserved in FIS directory if the
image already exists, or the length of the last loaded
file. If neither are set, it must be specified.</entry>
@@ -2580,11 +2580,11 @@ Delete image ‘junk’ - contin
</informaltable>
</refsect1>
<refsect1>
<title>Description</title>
<para>This command is used to write-protect (lock) a portion of flash memory,
-to prevent accidental overwriting of images. In order to make make any
modifications
+to prevent accidental overwriting of images. In order to make any modifications
to the flash, a matching <command>fis unlock</command> command must be
issued. This command is optional and will only be provided on hardware
which can support write-protection of the flash space.</para>
<note>
<para>Depending on the system, attempting to write to write-protected flash
