diff --git a/prod/doc/analysis.hmac b/prod/doc/analysis.hmac
index a7459f4..6d2e382 100644
--- a/prod/doc/analysis.hmac
+++ b/prod/doc/analysis.hmac
@@ -184,7 +184,7 @@ the right:
Other | Check voltages; check for contamination around crystal
@@ -238,7 +238,7 @@ depending on how much code was successfully flashed.
The clock frequency of atben can be measured with an accuracy
-of about +/− 100 ppm using the program atrf-xtal. atrf-xtal
+of about +/− 100 ppm using the program atrf-xtal. atrf-xtal
runs directly on the Ben and measures the duration of packet transmissions.
The transmission time depends on the bit clock which is in turn derived
from the oscillator.
diff --git a/prod/doc/flash.hmac b/prod/doc/flash.hmac
index 515fb8c..87eb28e 100644
--- a/prod/doc/flash.hmac
+++ b/prod/doc/flash.hmac
@@ -28,8 +28,8 @@ The microcontroller of atusb contains firmware that must be
loaded before the testing process can commence. The firmware consists
of the following two parts:
- - The boot loader (via serial programming, using avrdude)
-
- The application (via DFU, using dfu-util)
+
- The boot loader (via serial programming, using avrdude)
+
- The application (via DFU, using dfu-util)
Note that atben has no microcontroller and therefore does not need
diff --git a/prod/doc/setup.hmac b/prod/doc/setup.hmac
index df4e7e8..bd2b868 100644
--- a/prod/doc/setup.hmac
+++ b/prod/doc/setup.hmac
@@ -37,13 +37,13 @@ and configuration process.
-For a DUT and reference device role, the ben-wpan utilities
+For a DUT and reference device role, the ben-wpan utilities
and the test scripts have to be installed on the PC. For flashing the
atusb application
-firmware, also dfu-util and the firmware binary are required.
+firmware, also dfu-util and the firmware binary are required.
The instructions below assume that a complete development environment
-is already present on the PC, including SDL and SDL_gfx.
+is already present on the PC, including SDL and SDL_gfx.
If any prerequisites are not met,
compilation will fail, and you'll have to install the corresponding
package and try again.
@@ -65,13 +65,13 @@ make install
A different directory prefix can be chosen by overriding the
-INSTALL_PREFIX variable, e.g.,
+INSTALL_PREFIX variable, e.g.,
make INSTALL_PREFIX=/usr install
Note that the test scripts expect ${INSTALL_PREFIX}/bin
-to be in PATH.
+to be in PATH.
@@ -80,7 +80,7 @@ to be in PATH.
The test scripts are in the directory prod/ of the
-ben-wpan project. They currently are designed to be run from
+ben-wpan project. They currently are designed to be run from
this directory. Therefore, all that's necessary is to check out the
repository, as shown above.
@@ -90,8 +90,8 @@ repository, as shown above.
-dfu-util is used to transfer the application firmware to
-atusb boards. To build dfu-util from source, run these
+dfu-util is used to transfer the application firmware to
+atusb boards. To build dfu-util from source, run these
commands:
@@ -104,7 +104,7 @@ make install
Note that some Linux distributions already provide a pre-compiled
-version of dfu-util, which could be used instead of building
+version of dfu-util, which could be used instead of building
it from source.
@@ -160,10 +160,10 @@ If using prod/Makefile to run the production test process,
the names of the drivers for DUT and reference device are defined
through variables at the beginning of the Makefile. In particular,
if the host name or IP address under which the Ben is reached differs from
-"ben", the value of ATBEN_DUT and ATUSB_REF will have be
-changed accordingly.
+"ben", the value of ATBEN_DUT and ATUSB_REF
+will have be changed accordingly.
-The Makefile also contains the variable SPECTRUM_MARGIN that
+The Makefile also contains the variable SPECTRUM_MARGIN that
defines how many dB of tolerance should be allowed below and above the
reference signal strength. The default is to allow a margin of 5 dB in
either direction.
@@ -179,9 +179,9 @@ configuration variables. If the names of the files containing the
-For a DUT and reference device role, the ben-wpan utilities
+For a DUT and reference device role, the ben-wpan utilities
have to be installed on a Ben. For flashing the atusb boot
-loader, also avrdude and the boot loader binary are needed.
+loader, also avrdude and the boot loader binary are needed.
The instructions below apply for OpenWrt and Jlime. For building
things from source, a cross-compilation toolchain has to be installed
@@ -205,7 +205,7 @@ ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub
-To build and install the ben-wpan tools on the Ben, first set
+To build and install the ben-wpan tools on the Ben, first set
up networking between the PC and the Ben. If you have not yet checked
out the project's repository, run these commands:
@@ -214,7 +214,7 @@ git clone git://projects.qi-hardware.com/ben-wpan.git
cd ben-wpan/tools
-If you have already checked out the repository, cd to
+If you have already checked out the repository, cd to
ben-wpan/tools/ and run
@@ -238,7 +238,7 @@ Finally, upload the tools to the Ben and install them under
make HOST=ben install
-Where ben is the host name or IP address assigned to the Ben.
+Where ben is the host name or IP address assigned to the Ben.
@@ -246,7 +246,7 @@ Where ben is the host name or IP address assigned to the Ben.
-The atusb boot loader is flashed using avrdude. A pre-compiled
+The atusb boot loader is flashed using avrdude. A pre-compiled
static binary (suitable for OpenWrt and Jlime) can be installed by running
the following two command on the Ben:
@@ -255,7 +255,7 @@ wget http://downloads.qi-hardware.com/people/werner/wpan/bindist/avrdude-5.10-de
tar -xz -C / -f avrdude-5.10-de72af351f661b538add81cbc9965278a2f8c40c.tar.gz
-Instructions for building avrdude from sources are
+Instructions for building avrdude from sources are
here.
diff --git a/prod/doc/test.hmac b/prod/doc/test.hmac
index 4d8b99d..0f05dff 100644
--- a/prod/doc/test.hmac
+++ b/prod/doc/test.hmac
@@ -80,7 +80,7 @@ Of these tests, only "LED" and "Spectrum" require operator input. The
other tests run without interaction.
The test scripts log the commands they execute and their output in the
-file _log.
+file _log.
|