diff --git a/INSTALL.linux b/INSTALL.linux
index de9b7ce4c..f3b9c630b 100644
--- a/INSTALL.linux
+++ b/INSTALL.linux
@@ -14,7 +14,7 @@ $ make install
 ==================================================
 
 2.1. Install with your preferred package manager:
-     (a) the development environment for your Linux distibution
+     (a) the development environment for your Linux distribution
          - mandatory: gcc, make, kernel header files, autoconf, autoconf-archive,
                       python(>=2.7)
          - optional:  git
diff --git a/NEWS b/NEWS
index 95f58b018..e06768010 100644
--- a/NEWS
+++ b/NEWS
@@ -44,7 +44,7 @@
 - adds and updates information for multiple supported and unsupported
   devices
 - translation updates for British English, French, German, Italian and
-  Ukranian
+  Ukrainian
 - `scanimage`: documents the JPEG compression level
 - minor improvements documenting build requirements
 
@@ -56,7 +56,7 @@
   required support is not available, `configure` will exit with an
   error.
 - improves checking for libjpeg version dependent requirements
-- has been made reproducable (#228)
+- has been made reproducible (#228)
 - fixes build issues on MinGW
 
 ### Miscellaneous
@@ -338,7 +338,7 @@ New with 1.0.18, released 2006-07-02:
   microtek2, mustek_pp, niash, plustek, snapscan, sp15c, test, u12, umax1220u.
 * Scanimage batch mode fixes.
 * Scanner lists contain USB vendor/product ids and some statistics now.
-* Udev/hotplug lists are generated autmatically from the .desc files now.
+* Udev/hotplug lists are generated automatically from the .desc files now.
 * Portability fixes (especially for DragonFlyBSD and HP/UX).
 * Build system updates.
 * Updated translations.
@@ -414,7 +414,7 @@ New with 1.0.14, released 2004-05-01:
 New with 1.0.13, released 2003-11-22:
 
 * New backends: mustek_pp_ccd (for Mustek parport CCD scanners),
-  plustek_pp (for Plustek parport scanners, splitted from the plustek backend).
+  plustek_pp (for Plustek parport scanners, split from the plustek backend).
 * Updated backends: avision, canon630u, coolscan, epson, fujitsu, gphoto2,
   gt68xx, hp, hp5400, mustek, mustek_pp, pie, plustek, snapscan, teco2, test,
   umax, umax_pp.
@@ -484,7 +484,7 @@ New with 1.0.9, released 2002-10-24:
 * New tool to create gamma tables (gamma4scanimage).
 * Support for ICC profiles for scanimage.
 * USB scanner should work on all systems supported by libusb now.
-* Portability fixes (especially for big-endian sytems, Irix, OpenStep, OS/2,
+* Portability fixes (especially for big-endian systems, Irix, OpenStep, OS/2,
   Solaris).
 * New and updated translations for various backends.
 * New system for generating lists of manufacturers/backends.
@@ -548,7 +548,7 @@ New with 1.0.6, released 2001-11-05:
 New with 1.0.5, released 2001-07-01:
 
 * New backends: bh (Bell+Howell Copiscan II series), dc240 (Kodak DC240
-  Digital Camera), sm3600 (Microtek ScanMaker 3600), umax_pp (Umax paralell
+  Digital Camera), sm3600 (Microtek ScanMaker 3600), umax_pp (Umax parallel
   port scanners).
 * Updated backends: artec (v0.5.16), dc25 (v1.2), dll (v1.0.3),
   epson (v0.2.08), hp (v0.94), microtek (v0.12.3), microtek2(v0.9),
@@ -577,7 +577,7 @@ New with 1.0.4, released 2000-12-21:
   hp (v0.93), mustek (v1.0-102), mustek_pp (v0.9-devel), plustek (v0.38),
   sharp (v0.32), umax (v1.0-21).
 * Moved frontends xscanimage and xcam to a new package (sane-frontends).
-* Added authentification with encrypted passwords.
+* Added authentication with encrypted passwords.
 * Installation of shared libraries on AIX is supported now.
 * Fixed compilation bugs on Irix and FreeBSD.
 * Better debug output on platforms not supporting vararg macros.
@@ -685,7 +685,7 @@ New with 1.01:
    o larger buffer acquired (speeds up scanning slightly)
    o for SE models minimal resolution increased from 60 dpi to 75 dpi
    o for SE models 75 dpi in color mode is no longer used as the newer
-     firware version seems to be even more buggy
+     firmware version seems to be even more buggy
    o bug in calculation of gamma table corrected (applies only to SE models,
      NOT related to the overflow problem which was corrected via CLIP( ) )
    o default resolution is now set according to the minimal resolution
@@ -894,7 +894,7 @@ New with 0.74:
  o changed the default for the resolution
  o The values for the SANE_Params struct are calculated more precisely
  o dito the number of scan lines that fit into the frontend buffer
- o changed some return stati ( replaced SANE_STATUS_INVAL with
+ o changed some return statuses ( replaced SANE_STATUS_INVAL with
    SANE_STATUS_IO_ERROR where the first one is not allowed)
  o completely rewrote the end of scan and cancel scan handling
  o fixed another bug that caused xscanimage to crash with sigsegv
@@ -913,7 +913,7 @@ New with 0.74:
   o Quality calibration / calibration by driver now works for same scanners.
      - added selection for type of shading data calculation
   o Solved problem with black area at top of the image
-    (happend only with some SCSI-adapters).
+    (happened only with some SCSI-adapters).
   o Added gamma download format type 0 and type 1 for older scanners.
   o Added Astra 1220S as supported scanner:
      - added 36 gamma input bits support for Astra 1220S
@@ -969,7 +969,7 @@ New with 0.73:
        - 3-pass scanners
        - more than 8 bit per color output data. Provisions are made here
          and there in the code, to support more than 8 bit, but that's
-         uncomplete.
+         incomplete.
 
 * configure --disable-static should now work as expected.
 
diff --git a/PROBLEMS b/PROBLEMS
index 4eef21a19..62466c173 100644
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -17,6 +17,6 @@ Last update: 2006-01-05
 
   saned is not intended to be exposed to the internet or other non-trusted
   networks.  Make sure that access is limited by tcpwrappers and/or a firewall
-  setup. Don't depend only on saned's own authentification.  Don't run saned
+  setup. Don't depend only on saned's own authentication.  Don't run saned
   as root if it's not necessary. And do not install saned as setuid root.
   Read man saned(8) for details.
diff --git a/README.netbsd b/README.netbsd
index dfe52ac66..520c341b2 100644
--- a/README.netbsd
+++ b/README.netbsd
@@ -48,7 +48,7 @@ uscanner driver can't detect the vendor and product ids automatically, it's
 necessary to add the name of the device file to the backends's configuration
 file. Some backends also need the vendor and product id of the scanner.
 
-Some backends won't work with the uscanner driver becasue they need USB
+Some backends won't work with the uscanner driver because they need USB
 control messages. Use libusb instead.
 
 Parport-scanners:
diff --git a/README.os2 b/README.os2
index ab6421dc6..978f1d3c7 100644
--- a/README.os2
+++ b/README.os2
@@ -36,7 +36,7 @@ SUPPORT
 I'm sorry to tell you that it is hard for me to help you: if your scanner
 doesn't work or your problem can't be reproduced on my pc, there are high
 choices that I can't fix the bug. Most problems are specific to same PC/scanner
-combinations, and can't be solved without having a full developement enviroment
+combinations, and can't be solved without having a full development environment
 and programming experience.
 
 I have setup a mailing list for users, where I hope most people can find an
diff --git a/README.solaris b/README.solaris
index 12dae0505..90a6edf40 100644
--- a/README.solaris
+++ b/README.solaris
@@ -24,7 +24,7 @@ make install
 It was also required to add a generic USB kernel driver. I had to look for
 my scanner device name in output of
 prtconf -D -v
-command. My scanner is Plustek UT24 and the apropriate part of output looked
+command. My scanner is Plustek UT24 and the appropriate part of output looked
 like this:
 name='compatible' type=string items=8 value='usb7b3,17.100' + ...
 I had to remove the not used kernel driver
@@ -58,7 +58,7 @@ downloaded from www.sun.com/solaris for free.
 In my opinion it is important to be cautious when using scanner or just libusb
 on important Solaris machines (especially multi-processor ones), because unlike
 in other systems, Solaris kernel is fully preemtible, what means, that many
-instances of the same driver can ran simultanously - it's dangerous, when
+instances of the same driver can run simultaneously - it's dangerous, when
 drivers are not perfect. And Solaris USB framework is absolutely new, so it can
 contain bugs. I tried to crash my Solaris using USB subsystem and SANE, I didn't
 manage to, but it doesn't mean, it's impossible.
diff --git a/README.unixware2 b/README.unixware2
index b76070d9a..3e7440996 100644
--- a/README.unixware2
+++ b/README.unixware2
@@ -9,7 +9,7 @@ Please send Email to wolfgang@rapp-informatik.de to receive.
 What you need to build xane on Unixware 2.x
 - gnu make
 
-You dont't need gcc. All is build with the standard Unixware cc and
+You don't need gcc. All is build with the standard Unixware cc and
 libs!!
 
 For the X-frontends xscanimage and xsane (separately distributed) you need
@@ -38,8 +38,8 @@ are build.It's also necessary for mathematic lib -lm .  Not doing this
 will bring runtime errors like missimg usleep or pow function.
 
 ATTENTION:!!! libucb.a of Unixware 2.x has a buggy readdir function so
-it is recommanded to remove readdir.o from libucb.a with ar -d
-readdir.o libucb.a Often used and neded functions from libucb.a are
+it is recommended to remove readdir.o from libucb.a with ar -d
+readdir.o libucb.a Often used and needed functions from libucb.a are
 strncasecmp or getpagesize.
 
 If you use -I/usr/ucbinclude it is also a good idea to move
@@ -48,7 +48,7 @@ first and some sources will not compile.
 
 Then you can run make with GNU make.
 
-After this say su and then ist good to say
+After this say su and then it's good to say
 LD_RUN_PATH=/usr/local/lib export LD_RUN_PATH
 
 after this you can install with
diff --git a/README.unixware7 b/README.unixware7
index 7a48233b1..55ac804f5 100644
--- a/README.unixware7
+++ b/README.unixware7
@@ -18,7 +18,7 @@ found here:
 
 However, please note that the SANE package that is available from the
 Skunkware server will most likely contain the latest stable version of
-SANE. Since SANE is continously being worked on, you might want to download
+SANE. Since SANE is continuously being worked on, you might want to download
 the latest source from the Git repository and build the source yourself.
 
 To build SANE on a UnixWare 7.1.X system the following packages are required:
diff --git a/README.windows b/README.windows
index 4715047d0..f30af6818 100644
--- a/README.windows
+++ b/README.windows
@@ -44,7 +44,7 @@ If you have more than one scanner, you should do the following:
 
 Run "scanimage > out.pnm" to get a scan.
 
-xscanimage ans XSane have been reported to compile and run in the past
+xscanimage and XSane have been reported to compile and run in the past
 under Cygwin.
 
 Notes
diff --git a/README.zeta b/README.zeta
index 9c0028e6c..e8680a436 100644
--- a/README.zeta
+++ b/README.zeta
@@ -2,7 +2,7 @@ SANE and Zeta
 -------------
 
 The Zeta port is based on existing BeOS port, with some changes
-to accomodate yellowTAB's internal build procedure, and some new
+to accommodate yellowTAB's internal build procedure, and some new
 conventions brought up by Zeta.
 
 Cf. README.beos for more historical stuff.
diff --git a/doc/backend-writing.txt b/doc/backend-writing.txt
index 5823661a6..cb2a97142 100644
--- a/doc/backend-writing.txt
+++ b/doc/backend-writing.txt
@@ -185,7 +185,7 @@ sane-backends/include/
        used by several backends.
      * sanei_*:
        Sanei (SANE internal) headers. Needed for code used in several backends
-       like USB access. For more details, see the documentaion on the SANE website.
+       like USB access. For more details, see the documentation on the SANE website.
 
 sane-backends/japi/
      Contains Java interface for SANE. See README.JAVA for details.
@@ -199,7 +199,7 @@ sane-backends/po/
 
 sane-backends/sanei/
      Sanei (SANE internal) code. Needed for code used in several backends
-     like USB access. For more details, see the documentaion on the SANE
+     like USB access. For more details, see the documentation on the SANE
      website.
 
 sane-backends/testsuite/
@@ -310,7 +310,7 @@ PROGRAMMING
   the doc/ directory.
 
 * Initialize global variables explicitly in sane_init. Keep in mind that
-  sane_init can be called more than once (if sane_exit is called everytime
+  sane_init can be called more than once (if sane_exit is called every time
   after sane_init). Therefore don't depend on automatic initialization to
   0 / NULL.
 
diff --git a/doc/descriptions-external/utsushi.desc b/doc/descriptions-external/utsushi.desc
index 231711d43..c32b529a7 100644
--- a/doc/descriptions-external/utsushi.desc
+++ b/doc/descriptions-external/utsushi.desc
@@ -445,25 +445,25 @@
 :interface "USB"
 :usbid     "0x04b8" "0x0165"
 :status    :good
-:comment   "propably one of DS-410, DS-535, DS-575W, DS-775"
+:comment   "probably one of DS-410, DS-535, DS-575W, DS-775"
 
 :model     "PID 0167"
 :interface "USB"
 :usbid     "0x04b8" "0x0167"
 :status    :good
-:comment   "propably one of DS-410, DS-535, DS-575W, DS-775"
+:comment   "probably one of DS-410, DS-535, DS-575W, DS-775"
 
 :model     "PID 0168"
 :interface "USB"
 :usbid     "0x04b8" "0x0168"
 :status    :good
-:comment   "propably one of DS-410, DS-535, DS-575W, DS-775"
+:comment   "probably one of DS-410, DS-535, DS-575W, DS-775"
 
 :model     "PID 0169"
 :interface "USB"
 :usbid     "0x04b8" "0x0169"
 :status    :good
-:comment   "propably one of DS-410, DS-535, DS-575W, DS-775"
+:comment   "probably one of DS-410, DS-535, DS-575W, DS-775"
 
 :model     "PID 016B"
 :interface "USB"
@@ -475,13 +475,13 @@
 :interface "USB"
 :usbid     "0x04b8" "0x016d"
 :status    :good
-:comment   "propably one of ES-55R, ES-65WR"
+:comment   "probably one of ES-55R, ES-65WR"
 
 :model     "PID 016F"
 :interface "USB"
 :usbid     "0x04b8" "0x016f"
 :status    :good
-:comment   "propably one of ES-55R, ES-65WR"
+:comment   "probably one of ES-55R, ES-65WR"
 
 :model     "PID 0176"
 :interface "USB"
diff --git a/doc/descriptions/unsupported.desc b/doc/descriptions/unsupported.desc
index 03788c47a..7748313a6 100644
--- a/doc/descriptions/unsupported.desc
+++ b/doc/descriptions/unsupported.desc
@@ -709,7 +709,7 @@
 :interface "USB"
 :usbid "0x06dc" "0x0012"
 :status :unsupported
-:comment "Unsuported. See link for details."
+:comment "Unsupported. See link for details."
 
 :model "ColorPage HR8"
 :url "unsupported/genius-colorpage-hr8.html"
@@ -2255,7 +2255,7 @@
 :interface "Parport"
 :status :unsupported
 :url "http://www.autistici.org/tamarhack/"
-:comment "Unsupported at the moment. See link for a project for that scanner taht may support it in future."
+:comment "Unsupported at the moment. See link for a project for that scanner that may support it in future."
 
 :model "Artiscan 9600 pro 36"                ; name models for above-specified mfg.
 :interface "Parport"
diff --git a/doc/sane-usb.man b/doc/sane-usb.man
index cb65c7f13..4ed085e3a 100644
--- a/doc/sane-usb.man
+++ b/doc/sane-usb.man
@@ -4,7 +4,7 @@
 sane\-usb \- USB configuration tips for SANE
 .SH DESCRIPTION
 This manual page contains information on how to access scanners with a USB
-interface. It focusses on two main topics: getting the scanner detected by the
+interface. It focuses on two main topics: getting the scanner detected by the
 operating system kernel and using it with SANE.
 .PP
 This page applies to USB most backends and scanners, as they use the generic
diff --git a/doc/saned.man b/doc/saned.man
index d01990111..aff14d95a 100644
--- a/doc/saned.man
+++ b/doc/saned.man
@@ -254,7 +254,7 @@ to the systemd journal. The systemd support
 requires compilation with the systemd-devel package
 installed on the system. this is the preferred option.
 
-Saned can be used wih systemd without the systemd integration
+Saned can be used with systemd without the systemd integration
 compiled in, but then logging of debug information is not supported.
 
 The systemd configuration is different for the 2 options, so
@@ -362,7 +362,7 @@ WantedBy=sockets.target
 .PP
 The second file to be added is
 .I saned@.service
-This one differes from the sersion with systemd integration compiled in:
+This one differs from the version with systemd integration compiled in:
 .PP
 .RS
 .ft CR