Fix random minor spelling errors

now that we have CI telling where the problems are, fix it.

Signed-off-by: Robin Getz <[email protected]>

Author: rgetz

CI/azure/generateDocumentationAndDeploy.sh.in

@@ -8,7 +8,7 @@ set -x
 #
 # Preconditions:
 # - Packages doxygen graphviz must be installed.
-# - An gh-pages branch should already exist. See below for mor info on how to
+# - An gh-pages branch should already exist. See below for more info on how to
 #   create a gh-pages branch.
 #
 # This script will generate Doxygen documentation and push the documentation to

README_BUILD.md

@@ -82,7 +82,7 @@ Cmake Options       | Default | Description                                    |
 `WITH_ZSTD`               | OFF | Support for ZSTD compressed metadata    |
 
 
-Options which effect iiod only. These are only avalible on Linux.
+Options which effect iiod only. These are only available on Linux.
 
 Cmake Options       | Default | Description                                    |
 ------------------- | ------- | ---------------------------------------------- |

bindings/cpp/iiopp.h

@@ -40,7 +40,7 @@
  * - Error handling (error codes are checked and turned into exceptions).
  * - Functions that may return \c NULL for "no string" are explicit by returning an <tt>std::optional</tt>.
  * - Iterators for idiomatic access to devices of context and channels of devices.
- * - Iterators for atributes.
+ * - Iterators for attributes.
  * - Implicit conversion to the wrapped C-types, so C++ instances can easily be passed to the C-API.
  *
  * @warning All objects live in the @ref iiopp::Context that created them. When a context gets destroyed (when

bindings/csharp/Device.cs

@@ -450,7 +450,7 @@ public Attr find_buffer_attribute(string attribute)
             return new DeviceBufferAttr(dev, Marshal.PtrToStringAnsi(attr));
         }
 
-        /// <summary>Finds the channel attribute coresponding to the given filename from the current device.</summary>
+        /// <summary>Finds the channel attribute corresponding to the given filename from the current device.</summary>
         /// <param name="filename">The name of the attribute.</param>
         /// <param name="chn_ptr">Output variable. It will contain a pointer to the resulting <see cref="iio.Channel"/>.</param>
         /// <param name="attr">Output variable. It will contain a pointer to the resulting <see cref="iio.ChannelAttr"/>.</param>

bindings/csharp/mainpage.dox

@@ -15,7 +15,7 @@ open-source, commercial or non-commercial applications.
 The full terms of the library license can be found at: http://opensource.org/licenses/LGPL-2.1 and the iio-utils license can be found at: https://opensource.org/licenses/GPL-2.0
 
 @section code_model Code Model
-The basic bricks of the libiio API, and therefore the C# bindings are the the iio namepace, and the classes of that nameplace: iio.Channel, iio.Context, iio.Device, iio.IOBuffer, iio.Trigger, and iio.Attr (channel or device attributes).
+The basic bricks of the libiio API, and therefore the C# bindings are the the iio namespace, and the classes of that nameplace: iio.Channel, iio.Context, iio.Device, iio.IOBuffer, iio.Trigger, and iio.Attr (channel or device attributes).
 
 ![Caption text](doc/codemodel.svg)
 

bindings/python/doc/iio_attr.rst

@@ -1,7 +1,7 @@
 iio_attr
 ======================
 | iio_attr is part of the Libiio package, a library that has been developed to ease the development of software interfacing Linux Industrial I/O (IIO) devices.
-| This tool is written using the libiio Python bindings. It works in a very similar way of how the base iio_attr works. You can find more informations about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_attr>`_.
+| This tool is written using the libiio Python bindings. It works in a very similar way of how the base iio_attr works. You can find more information about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_attr>`_.
 
 .. automodule:: iio_attr
    :members:

bindings/python/doc/iio_info.rst

@@ -1,7 +1,7 @@
 iio_info
 =====================
 | iio_info is part of the Libiio package, a library that has been developed to ease the development of software interfacing Linux Industrial I/O (IIO) devices.
-| This tool is written using the libiio Python bindings. It works in the same way as the base iio_info works. You can find more informations about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_info>`_.
+| This tool is written using the libiio Python bindings. It works in the same way as the base iio_info works. You can find more information about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_info>`_.
 
 .. automodule:: iio_info
    :members:

bindings/python/doc/iio_readdev.rst

@@ -1,7 +1,7 @@
 iio_readdev
 =====================
 | iio_readdev is part of the Libiio package, a library that has been developed to ease the development of software interfacing Linux Industrial I/O (IIO) devices.
-| This tool is written using the libiio Python bindings. It works in the same way as the base iio_readdev works. You can find more informations about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_readdev?s[]=readdev>`_.
+| This tool is written using the libiio Python bindings. It works in the same way as the base iio_readdev works. You can find more information about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_readdev?s[]=readdev>`_.
 
 .. automodule:: iio_readdev
    :members:

bindings/python/doc/iio_writedev.rst

@@ -1,7 +1,7 @@
 iio_writedev
 =====================
 | iio_writedev is part of the Libiio package, a library that has been developed to ease the development of software interfacing Linux Industrial I/O (IIO) devices.
-| This tool is written using the libiio Python bindings. It works in the same way as the base iio_writedev works. You can find more informations about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_writedev>`_.
+| This tool is written using the libiio Python bindings. It works in the same way as the base iio_writedev works. You can find more information about it on this `page <https://wiki.analog.com/resources/tools-software/linux-software/libiio/iio_writedev>`_.
 
 .. automodule:: iio_writedev
    :members:

cmake/LinuxPackaging.cmake

@@ -41,11 +41,11 @@ endif()
 # if we want to, and have the capabilities find what is needed,
 # based on what backends are turned on and what libraries are installed
 if(DEB_DETECT_DEPENDENCIES AND DPKG_CMD AND DPKGQ_CMD)
-	message(STATUS "querying installed packages on system for dependancies")
+	message(STATUS "querying installed packages on system for dependencies")
 	execute_process(COMMAND "${DPKG_CMD}" --print-architecture 
 		OUTPUT_VARIABLE CPACK_DEBIAN_PACKAGE_ARCHITECTURE
 		OUTPUT_STRIP_TRAILING_WHITESPACE)
-	# don't add a package dependancy if it is not installed locally
+	# don't add a package dependency if it is not installed locally
 	# these should be the debian package names
 	set(PACKAGES "libc6")
 	if (WITH_LOCAL_BACKEND)
@@ -64,7 +64,7 @@ if(DEB_DETECT_DEPENDENCIES AND DPKG_CMD AND DPKGQ_CMD)
 		set(PACKAGES "${PACKAGES} libserialport0")
 	endif()
 	# find the version of the installed package, which is hard to do in
-	# cmake first, turn the list into an list (seperated by semicolons)
+	# cmake first, turn the list into an list (separated by semicolons)
 	string(REGEX REPLACE " " ";" PACKAGES ${PACKAGES})
 	# then iterate over each
 	foreach(package ${PACKAGES})
@@ -103,7 +103,7 @@ if(DEB_DETECT_DEPENDENCIES AND DPKG_CMD AND DPKGQ_CMD)
 						DPKGQ_VER ${DPKGQ_VER})
 				string(REGEX REPLACE "'" "" DPKGQ_VER
 						${DPKGQ_VER})
-				# build the string for the Debian dependancy
+				# build the string for the Debian dependency
 				set(CPACK_DEBIAN_PACKAGE_DEPENDS
 					"${CPACK_DEBIAN_PACKAGE_DEPENDS}"
 					"${match} (>= ${DPKGQ_VER}), ")

dns_sd_windows.c

@@ -187,7 +187,7 @@ static int open_client_sockets(int *sockets, unsigned int max_sockets)
  *  - IPv4 "address" record (A) specifying IPv4 address of a given host
  *  - IPv6 "address" record (AAAA) specifying IPv6 address of a given host
  * It's this routine that gets called, and needs to stitch things together
- * The DNS host doesn't necessary need to be the acutal host (but for
+ * The DNS host doesn't necessary need to be the actual host (but for
  * mdns - it usually is.
  */
 static int query_callback(int sock, const struct sockaddr *from, size_t addrlen,

doc/index.html.in

@@ -199,7 +199,7 @@
     devices. IIO started as a <a href=
     "https://www.kernel.org/doc/html/latest/driver-api/iio/index.html">Linux
     kernel subsystem</a> to support for devices that included
-    analog-to-digital convertors (ADCs) and/or digital-to-analog convertors
+    analog-to-digital converters (ADCs) and/or digital-to-analog converters
     (DACs). While the libIIO continues to provide an easy interface to the
     Linux kernel IIO subsystem, it has also expanded beyond that, and is now
     just as common to see this used inside an embedded system or hypervisor as

iiod/dns-sd.c

@@ -310,7 +310,7 @@ void start_avahi(struct thread_pool *pool, uint16_t port)
 	avahi.name = NULL;
 	avahi.port = port;
 
-	/* In case dbus, or avahi deamon are not started, we create a thread
+	/* In case dbus, or avahi daemon are not started, we create a thread
 	 * that tries a few times to attach, if it can't within the first
 	 * minute, it gives up.
 	 */

local.c

@@ -926,7 +926,7 @@ static int local_open(const struct iio_device *dev,
 
 	/*
 	 * Set watermark to the buffer size; the driver will adjust to its
-	 * maximum if it's too high without issueing an error.
+	 * maximum if it's too high without issuing an error.
 	 */
 	ret = local_write_dev_attr(dev, "buffer/watermark",
 				   buf, strlen(buf) + 1, false);

mainpage.dox

@@ -11,7 +11,7 @@ License, version 2 or (at your option) any later version.
 This open-source license allows anyone to use the library for proprietary or
 open-source, commercial or non-commercial applications.
 
-Seperately, the IIO Library also includes a set of test examples and utilities, (collectively known as iio-utils) which are developed and released under the terms of the GNU General Public License, version 2 or (at your option) any later version.
+Separately, the IIO Library also includes a set of test examples and utilities, (collectively known as iio-utils) which are developed and released under the terms of the GNU General Public License, version 2 or (at your option) any later version.
 
 The full terms of the library license can be found at: http://opensource.org/licenses/LGPL-2.1 and the iio-utils license can be found at: https://opensource.org/licenses/GPL-2.0
 
@@ -31,7 +31,7 @@ A C++ API is provided in @ref iiopp.h
 @endif
 
 @section scan_contexts Scanning for IIO contexts
-The first step when dealing with a collection of IIO devices (known as a context) is to find the context. This can be connected via usb, network, serial or local. Having these different connectivity options could prove to be problematic, but libiio abstracts the low level communications away, and allows you just to find contexts, and talk to devices without being interested in the low level aspects. Many find this convinent to develop applications and algorithms on a host, and quickly move to an embedded Linux system without having to change any code.
+The first step when dealing with a collection of IIO devices (known as a context) is to find the context. This can be connected via usb, network, serial or local. Having these different connectivity options could prove to be problematic, but libiio abstracts the low level communications away, and allows you just to find contexts, and talk to devices without being interested in the low level aspects. Many find this convenient to develop applications and algorithms on a host, and quickly move to an embedded Linux system without having to change any code.
 
 To find what IIO contexts are available, use the following:
 - iio_create_scan_context(): Create a iio_scan_context object. Depending on what backends were enabled with compiling the library, some of them may not be available. The first argument to this function is a string which is used as a filter ("usb:", "ip:", "local:", "usb:ip", where the default (NULL) means any backend that is compiled in).

man/iio_common_cmds.1

@@ -15,4 +15,4 @@ on your system are up to date. This is also useful when reporting bugs.
 Scan for available IIO contexts, optional arg of specific backend(s) 'ip', 'usb' or 'ip:usb'.
 Specific options for USB include Vendor ID, Product ID to limit scanning to specific devices 'usb=0456,b673'.
 vid,pid are hexadecimal numbers (no prefix needed), "*" (match any for pid only)
-If no argument is given, it checks all that are availble.
+If no argument is given, it checks all that are available.

man/make_man.sh.in

@@ -32,7 +32,7 @@ cat <<EOF
 .\" <http://www.gnu.org/licenses/>.
 .\" %%%LICENSE_END
 .\"
-.\" This file is autogenerated, and should not be editted
+.\" This file is autogenerated, and should not be edited
 .\"
 .if n .po 0
 .TH INTRO 3LIBIIO "@CMAKE_DATE@" "libiio-@LIBIIO_VERSION_MAJOR@.@LIBIIO_VERSION_MINOR@"

utilities.c

@@ -220,7 +220,7 @@ char *iio_strtok_r(char *str, const char *delim, char **saveptr)
 #elif defined(HAS_STRTOK_R)
 	return strtok_r(str, delim, saveptr);
 #else
-#error Need a implentation of strtok_r for this platform
+#error Need a implementation of strtok_r for this platform
 #endif
 }