summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2007-02-18 16:46:46 +0000
committerFelix Fietkau <nbd@openwrt.org>2007-02-18 16:46:46 +0000
commit4941b6c4bdc98e271eaa2600816b86ca54796a59 (patch)
tree6274e6840e0a0df67e4fc41013dfab07dfa1d1d4 /docs
parent912e5867ef2685298e547972d968458f600be969 (diff)
downloadmtk-20170518-4941b6c4bdc98e271eaa2600816b86ca54796a59.zip
mtk-20170518-4941b6c4bdc98e271eaa2600816b86ca54796a59.tar.gz
mtk-20170518-4941b6c4bdc98e271eaa2600816b86ca54796a59.tar.bz2
add documentation fixes from #1285
SVN-Revision: 6319
Diffstat (limited to 'docs')
-rw-r--r--docs/adding.tex16
-rw-r--r--docs/init-scripts.tex4
2 files changed, 10 insertions, 10 deletions
diff --git a/docs/adding.tex b/docs/adding.tex
index 34e13ae..2695a76 100644
--- a/docs/adding.tex
+++ b/docs/adding.tex
@@ -121,15 +121,15 @@ Scroll over the firmware to find printable words that can be significant.
\subsubsection{Amount of flash memory}
-Linux can hardly fit in a 2MB flash device, once you have open the device and
-located the flash chip, try to find other the Internet its characteristics. If
+Linux can hardly fit in a 2MB flash device, once you have opened the device and
+located the flash chip, try to find its characteristics on the Internet. If
your flash chip is a 2MB or less device, your device is most likely to run a
proprietary OS such as WindRiver VxWorks, or a custom manufacturer OS like Zyxel ZynOS.
-OpenWrt does not currently run on devices which have equal or less than 2MB of
-flash memory. This limitation will probably not be worked around since those
-devices are most of the time micro routers, or Wireless Access Points, which are
-not the main OpenWrt target.
+OpenWrt does not currently run on devices which have 2MB or less of flash memory.
+This limitation will probably not be worked around since those devices are most
+of the time micro-routers, or Wireless Access Points, which are not the main
+OpenWrt target.
\subsubsection{Pluging a serial port}
@@ -140,8 +140,8 @@ easily notice if the device uses a Linux kenrel or something different.
\subsection{Finding and using the manufacturer SDK}
Once you are sure your device run a Linux based firmware, you will be able to start
-hacking on it. If the manufacturer respect the GPL, it will have release with the
-device, a Sample Development Kit.
+hacking on it. If the manufacturer respected the GPL, it will have released a Sample
+Development Kit with the device.
\subsubsection{GPL violations}
diff --git a/docs/init-scripts.tex b/docs/init-scripts.tex
index e1d96a2..ea74ded 100644
--- a/docs/init-scripts.tex
+++ b/docs/init-scripts.tex
@@ -24,8 +24,8 @@ This is done by the wrapper script \texttt{/etc/rc.common}.
script should provide. \texttt{start()} is called when the user runs \texttt{/etc/init.d/httpd start}
or (if the script is enabled and does not override this behavior) at system boot time.
-Enabling and disabling init scripts is done by running \texttt{/etc/init.d/\textit{name} start}
-or \texttt{/etc/init.d/\textit{name} stop}. This creates or removes symbolic links to the
+Enabling and disabling init scripts is done by running \texttt{/etc/init.d/\textit{name} enable}
+or \texttt{/etc/init.d/\textit{name} disable}. This creates or removes symbolic links to the
init script in \texttt{/etc/rc.d}, which is processed by \texttt{/etc/init.d/rcS} at boot time.
The order in which these scripts are run is defined in the variable \texttt{START} in the init