summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThom Johansen <thomj@rockbox.org>2007-12-13 22:51:27 +0000
committerThom Johansen <thomj@rockbox.org>2007-12-13 22:51:27 +0000
commit10d0344e296eeb9259e9b609bb9b656ba1d7e42a (patch)
tree1235ff80ba0306a7dc2121b67403c7f3c2f00c5d
parent88d85c8a9fd51fc02b49e93df0796fbecb60e2f3 (diff)
downloadrockbox-10d0344e296eeb9259e9b609bb9b656ba1d7e42a.zip
rockbox-10d0344e296eeb9259e9b609bb9b656ba1d7e42a.tar.gz
rockbox-10d0344e296eeb9259e9b609bb9b656ba1d7e42a.tar.bz2
rockbox-10d0344e296eeb9259e9b609bb9b656ba1d7e42a.tar.xz
FS #8315 and FS #8316, plus some of my own small changes. Pretty much just minor language rewrites.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@15919 a1c6a512-1295-4272-9138-f99709370657
-rw-r--r--manual/advanced_topics/archos-flashing.tex20
-rw-r--r--manual/advanced_topics/main.tex2
-rw-r--r--manual/configure_rockbox/sound_settings.tex2
-rw-r--r--manual/getting_started/iaudio_install.tex2
-rw-r--r--manual/getting_started/installation.tex2
-rw-r--r--manual/getting_started/main.tex2
-rw-r--r--manual/plugins/alpinecdc.tex2
-rw-r--r--manual/plugins/wormlet.tex12
-rw-r--r--manual/rockbox_interface/browsing_and_playing.tex2
-rw-r--r--manual/rockbox_interface/wps.tex2
10 files changed, 24 insertions, 24 deletions
diff --git a/manual/advanced_topics/archos-flashing.tex b/manual/advanced_topics/archos-flashing.tex
index fe36d53..c5b718a 100644
--- a/manual/advanced_topics/archos-flashing.tex
+++ b/manual/advanced_topics/archos-flashing.tex
@@ -88,7 +88,7 @@ your box.
There's one ultimate safety net to bring back boxes with even completely
garbled flash content: the \emph{UART} boot mod, which in turn requires the
-serial mod. It can bring the dead back to life, with that it's possible to
+serial mod. It can bring the dead back to life, in that it is possible to
re-flash independently from the outside, even if the flash is completely erased.
It has been used that during development, else Rockbox in flash wouldn't have
been possible. Extensive development effort went into the exploitation of the
@@ -100,10 +100,10 @@ perform these mods. Others may feel uncomfortable using the first tool
To comfort you a bit again: If you are starting with a known-good image, you
are unlikely to experience problems. The flash tools have been stable for quite
a while. Several users have used them extensively, even flashing while playing!
-Although it worked, it's not the recommended method.
+Although it worked, it is not the recommended method.
About the safety of operation: Since we have dual boot, you're not giving up
-the Archos firmware. It's still there when you hold
+the Archos firmware. It is still there when you hold
\opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for
everyone, you can still use the box, re-flash the second image with an updated
Rockbox copy, etc.
@@ -148,9 +148,9 @@ Long version, step by step procedure:
\item Use the \opt{recorder,recorderv2fm}{\ButtonFTwo\ settings or }the menu (\setting{General settings $\rightarrow$ File view $\rightarrow$ Show files}) to
configure seeing all files within the browser.
\item Connect the charger and make sure your batteries are also in good shape.
- That's just for security reasons, it's not that flashing needs more power.
+ This is purely for security reasons, flashing does not need more power than usual.
\item Run the \fname{firmware\_flash.rock} plugin. It again tells you about your
- flash and the file it's gonna program. After \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} it checks the file. Your
+ flash and the file it is going to program. After \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} it checks the file. Your
hardware mask value will be kept, it won't overwrite it. Hitting \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} gives you
a big warning. If we still didn't manage to scare you off, you can hit\opt{recorder,recorderv2fm}{\ButtonFThree}\opt{ondio}{\ButtonRight}\opt{player}{\ButtonRight} to actually program and verify. The programming takes just a few seconds. If
the sanity check fails, you have the wrong kind of boot ROM and are out of luck
@@ -158,7 +158,7 @@ Long version, step by step procedure:
\item In the unlikely event that the programming should give you any error, don't
switch off the box! Otherwise you'll have seen it working for the last time.
While Rockbox is still in DRAM and operational, we could upgrade the plugin via
- USB and try again. If you switch it off, it's gone.
+ USB and try again. If you switch it off, it is gone.
\end{enumerate}
\nopt{player}{
@@ -211,13 +211,13 @@ Here are the steps:
\item Normally, you'll simply download a \fname{.zip} distribution. Copy all the
content to the USB drive, replacing the old.
\item Force a disk boot by holding \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during power-up, or at least rolo into
- the new Rockbox version by \emph{Playing} the \fname{ajbrec.ajz}/fname{archos.mod} file. This may not always be necessary, but it's better to first run the
+ the new Rockbox version by \emph{Playing} the \fname{ajbrec.ajz}/fname{archos.mod} file. This may not always be necessary, but it is better to first run the
version you're about to flash. It is required if you are currently running
RomBox.
\item Just \emph{play} the \fname{.ucl} file in the \fname{.rockbox} directory,
- this will kick off the \fname{rockbox\_flash.rock} plugin. It's a bit similar
- to the other one, but it's made different to make the user aware. It will check
- the file, available size, etc. With \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} it's being programmed. No need for
+ this will kick off the \fname{rockbox\_flash.rock} plugin. It is a bit similar
+ to the other one, but it is made different to make the user aware. It will check
+ the file, available size, etc. With \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} it is being programmed. No need for
warning this time. If it goes wrong, you'll still have the permanent image.
\item When done, you can restart the box and hopefully your new Rockbox image.
\end{enumerate}
diff --git a/manual/advanced_topics/main.tex b/manual/advanced_topics/main.tex
index b2a7124..cc60f3f 100644
--- a/manual/advanced_topics/main.tex
+++ b/manual/advanced_topics/main.tex
@@ -381,7 +381,7 @@ Example of a configuration file:
\firmwarefilename. Note that Archos firmware can only read the first
ten characters of each filename in this process, so don't rename your old
firmware files with names like \firmwarefilename.\fname{old} and so on,
- because it's possible that the \dap{} will load a file other than the one
+ because it is possible that the \dap{} will load a file other than the one
you intended.
}
diff --git a/manual/configure_rockbox/sound_settings.tex b/manual/configure_rockbox/sound_settings.tex
index 3049ffe..6233616 100644
--- a/manual/configure_rockbox/sound_settings.tex
+++ b/manual/configure_rockbox/sound_settings.tex
@@ -171,7 +171,7 @@ change to customise your listening experience.
harmonics that they would generate.
The practical upshot of this is that MDB produces a more authentic sounding
- bass by tricking the brain in believing it's hearing tones that the
+ bass by tricking the brain into believing it is hearing tones that the
headphones or speakers aren't capable of reproducing. Try it and see
what you think.
diff --git a/manual/getting_started/iaudio_install.tex b/manual/getting_started/iaudio_install.tex
index 774006f..cdab94b 100644
--- a/manual/getting_started/iaudio_install.tex
+++ b/manual/getting_started/iaudio_install.tex
@@ -1,7 +1,7 @@
\fixme{This is merely a copy of the wiki page IaudioBoot, so this section needs
a more natural language and also error checking by Iaudio owners.}
-The \playername{} has a builtin boot loader which performs the
+The \playername{} has a built-in boot loader which performs the
firmware update, and can also access the hard drive via USB. Therefore the
Rockbox bootloader can be very minimalistic, without USB mode.
This also makes it less dangerous to install the Rockbox bootloader, as you can
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex
index 33a4a71..459f352 100644
--- a/manual/getting_started/installation.tex
+++ b/manual/getting_started/installation.tex
@@ -346,7 +346,7 @@ use.
}
\section{Updating Rockbox}
-Even if you don't use Rockbox Utility for updating Rockbox it's easy.
+Updating Rockbox is easy even if you don't use the Rockbox Utility.
Download a Rockbox build.
(The latest release of the Rockbox software will always be available from
\url{http://www.rockbox.org/download/}). Unzip the build to the root directory
diff --git a/manual/getting_started/main.tex b/manual/getting_started/main.tex
index 6eb8b3b..595c9b1 100644
--- a/manual/getting_started/main.tex
+++ b/manual/getting_started/main.tex
@@ -5,7 +5,7 @@ This is the manual for Rockbox. Rockbox is an open source firmware replacement
for a growing number of digital audio players. Rockbox aims to be considerably
more functional and efficient than your device's stock firmware while remaining
easy to use and customisable. Rockbox is written by users, for users. Not only
-is it free to use, it's also released under the GNU public license, which means
+is it free to use, it is also released under the GNU public license, which means
that it will always remain free both to use and to change.
Rockbox has been in development since 2001, and receives new features, tweaks
diff --git a/manual/plugins/alpinecdc.tex b/manual/plugins/alpinecdc.tex
index d493c55..008bb62 100644
--- a/manual/plugins/alpinecdc.tex
+++ b/manual/plugins/alpinecdc.tex
@@ -15,7 +15,7 @@ M-Bus radios have a DIN-style circular jack with 8 pins (7 in a $\sim$ 270 degre
circle, one in the center). A standard 5-pin DIN plug is OK for this, since we
don't use the other (power) pins.
-As OEM, they shuffled the pins around a bit, better check first if it's not
+As OEM, they shuffled the pins around a bit, better check first if it is not
genuine Alpine. The bus pin is pulled high to 12 volts with a $\sim$ 2kOhm resistor,
pulses driven low. Because it's open collector, this is not harmful to the
Archos.\\
diff --git a/manual/plugins/wormlet.tex b/manual/plugins/wormlet.tex
index 33fa9e4..c603dc2 100644
--- a/manual/plugins/wormlet.tex
+++ b/manual/plugins/wormlet.tex
@@ -87,7 +87,7 @@ Game controls:}
Use the control keys of your worm to navigate around obstacles and find
food. Worms do not stop moving except when dead. Dead worms are no fun.
Be careful as your worm will try to eat anything that you steer it
-across. It won't distinguish whether it's edible or not.
+across. It won't distinguish whether it is edible or not.
\begin{description}
\item[Food.]
@@ -157,7 +157,7 @@ games menu you can hit
On the right side of the game field is the score board. For each worm it
displays its status and its length. The top most entry displays the
state of worm 1, the second worm 2 and the third worm 3. When a worm
-dies it's entry on the score board turns black.
+dies its entry on the score board turns black.
\begin{description}
\item[Len:]
@@ -166,8 +166,8 @@ food it grows by one pixel for each step it moves.
\item[Hungry:]
That's the normal state of a worm. Worms are always
-hungry and want to eat. It's good to have a hungry
-worm since it means that your worm is alive. But it's
+hungry and want to eat. It is good to have a hungry
+worm since it means that your worm is alive. But it is
better to get your worm growing.
\item[Growing:]
@@ -183,11 +183,11 @@ This indicates that a worm has crashed against a wall.
\item[Argh:]
If the score board entry displays ``Argh!'' it
means the worm is dead because it tried to eat an ``argh''. Until we
-can make the worm say ``Argh!'' it's your job to say ``Argh!'' aloud.
+can make the worm say ``Argh!'' it is your job to say ``Argh!'' aloud.
\item[Wormed:]
The worm tried to eat another worm or even itself.
-That's why it's dead now. Making traps for other players with a worm
+That's why it is dead now. Making traps for other players with a worm
is a good way to get them out of the game.
\end{description}
diff --git a/manual/rockbox_interface/browsing_and_playing.tex b/manual/rockbox_interface/browsing_and_playing.tex
index 6beae05..affba1f 100644
--- a/manual/rockbox_interface/browsing_and_playing.tex
+++ b/manual/rockbox_interface/browsing_and_playing.tex
@@ -38,7 +38,7 @@ on the \dap{}.
\opt{h10,h10_5gb}{\note{
If your \dap{} is a MTP model, the Music folder where all your music is stored
may be hidden in the \setting{File Browser}. This may be fixed by either
-either changing it's properties (on a computer) to not hidden, or by changing
+either changing its properties (on a computer) to not hidden, or by changing
the \setting{Show Files} setting to all.
}}
diff --git a/manual/rockbox_interface/wps.tex b/manual/rockbox_interface/wps.tex
index 63719cb..fedd5e1 100644
--- a/manual/rockbox_interface/wps.tex
+++ b/manual/rockbox_interface/wps.tex
@@ -207,7 +207,7 @@ function in the \setting{File Context Menu}.
between 50\% and 200\%. 50\% means half the normal playback speed and the
pitch that's an octave lower than the normal pitch. 200\% means double
playback speed and the pitch that's an octave higher than the normal pitch.
- It's not possible to change the pitch without changing the playback speed and
+ It is not possible to change the pitch without changing the playback speed and
vice versa. Changing the pitch can be done in two modes: procentual and
semitone. Initially (after the \dap{} is switched on), procentual mode
is active.