fix typos

2 files changed, 18 insertions, 18 deletions

diff --git a/AUTHORS b/AUTHORS
index 1d024a7..8b02544 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -1,4 +1,4 @@
-Ineiev <ineiev@gnu.org>, super V 93, is the original author.
+Ineiev <ineiev@gnu.org>, is the original author.
 
 The firmware/usbconfig.h and firmware/usbdrv/* files constitute
 USB library for AVR; they are used with miguel as an external library,
@@ -10,7 +10,7 @@ of miguel, it's provided for reference.
 
 doc/texinfo.tex comes from Texinfo distribution under the GPLv3+,
 
-doc/gpl.texi is a copy of the GPL in the Texinfo format.
+doc/gpl-3.0.texi is a copy of the GPL in the Texinfo format.
 
 doc/*.png are excerpts from the complete schematic diagram exported
 from gschem and edited with Gimp.  doc/*.jpg are photos taken by
diff --git a/doc/miguel.texinfo b/doc/miguel.texinfo
index c437f92..7420bea 100644
--- a/doc/miguel.texinfo
+++ b/doc/miguel.texinfo
@@ -107,7 +107,7 @@ originally written by Ineiev @value{email}
 * Schematics::                    The board, and how it works.
 *   MCU::
 *   Noise Generator::
-*   Demultiplexors::
+*   Demultiplexers::
 *   Scanning Circuits::
 *   LED Switches::
 *   Power Distribution::
@@ -166,7 +166,7 @@ connected (through the computer) to the mains power line.
 @end itemize
 
 The next step is to figure out if it's feasible to resolve these
-issues.  Monitor eletronics are rather complicated and need high-speed
+issues.  Monitor electronics are rather complicated and need high-speed
 processing, but keyboard controller is no rocket science at all: a low
 cost microcontroller with some simple circuits can easily do the job.
 And after you decide to replace the controller, all aforementioned
@@ -225,7 +225,7 @@ active: 20 mA (no LED on), 30 mA (all LEDs on); sleeping: 20 uA
 
 Schematically, the keyboard controller features a 8-bit
 microcontroller, a noise generator used to get random numbers,
-a demultiplexor to add more output lines, lowpass filters connected
+a demultiplexer to add more output lines, lowpass filters connected
 to the keyboard matrix, switches to control keyboard LEDs, linear
 regulators to supply power, USB-specific circuits, and connectors.
 
@@ -237,7 +237,7 @@ figures below are excerpts of that complete diagram.
 @menu
 * MCU::
 * Noise Generator::
-* Demultiplexors::
+* Demultiplexers::
 * Scanning Circuits::
 * LED Switches::
 * Power Distribution::
@@ -299,11 +299,11 @@ counter produces decent random numbers with rates up to 100 kbit/s.
 
 When active, the generator draws about 10 mA from the Vdd source.
 
-@node Demultiplexors
-@section Demultiplexors
+@node Demultiplexers
+@section Demultiplexers
 
 In order to workaround the insufficient number of input-output lines
-in the MCU, two demultiplexors are used (@ref{fig:demux}).
+in the MCU, two demultiplexers are used (@ref{fig:demux}).
 
 U2 and U3 control the LEDs and scan the keyboard matrix.
 Note that the address signals of U3 are transposed for PCB layout
@@ -313,8 +313,8 @@ view: when it enables U3 and outputs 13 to the least significant half
 of PORTC, Y(13 + 16) = Y29 is drawn low.
 
 @float Figure,fig:demux
-@image{demux,4in,,2 demultiplexors}
-@caption{Demultiplexors.}
+@image{demux,4in,,2 demultiplexers}
+@caption{Demultiplexers.}
 @end float
 
 @node Scanning Circuits
@@ -429,7 +429,7 @@ of the tarball contains Gerber files.  You'll need @file{miguel.top},
 @end menu
 
 @node Board,Keyboard,Assembly,Assembly
-@section Assemblying the Board
+@section Assembling the Board
 
 This section mostly applies to the manual procedure.
 
@@ -454,7 +454,7 @@ before applying the power for the first time.
 
 This is especially true for the triple diodes.  I recommend testing
 the conductors connected to them: the respective lines should indicate
-the diode, the lines of the neighbouring devices should be
+the diode, the lines of the neighboring devices should be
 disconnected (unless joint with conductors like in D9).
 
 @end itemize
@@ -493,7 +493,7 @@ move from their places.
 @caption{Supporting keyboard.}
 @end float
 
-Columns are easily distinguished from the rows: they are layed out
+Columns are easily distinguished from the rows: they are laid out
 on the other film, and the number of the rows is much smaller (our
 controller supports no more than 8).
 
@@ -539,10 +539,10 @@ any keypresses.
 The leading software for uploading firmware into AVR seems to be
 @command{avrdude}
 (@url{https://savannah.nongnu.org/projects/avrdude}).  Sometimes I
-still use @command{uisp}, but it is not maintaned anymore and needs
+still use @command{uisp}, but it is not maintained anymore and needs
 patching to support newer chips.
 
-I program MCUs with a self-made Altera ByteBlaster, but
+I program MCUs with a self-made ByteBlaster, but
 @command{avrdude} supports many other programmers as well.  Please see
 @command{avrdude} documentation for details on how to upload firmware.
 
@@ -762,7 +762,7 @@ reports the keypresses.
 
 Another possibility is cycling the USB power line: when the controller
 encounters low VUSB level, it switches off until VUSB is high again.
-In this moed, no LEDs are active, no keys are scanned, and the
+In this mode, no LEDs are active, no keys are scanned, and the
 microcontroller puts itself in a sleeping mode.
 
 @node Benchmarks,Wire Loop,Software,Top
@@ -780,7 +780,7 @@ oscilloscope, with no special radio equipment involved.
 @node Wire Loop,Matrix Current,Benchmarks,Benchmarks
 @section Wire Loop
 
-This is the most simple test.  A loop of wire is layed on the
+This is the most simple test.  A loop of wire is laid on the
 keyboard and connected to the oscilloscope.
 
 @float Figure,fig:loop