documentation: Fix typos (found by codespell)

Signed-off-by: Stefan Weil <sw@weilnetz.de>

1 files changed, 3 insertions, 3 deletions

diff --git a/documentation/api/modules/nixio.README.html b/documentation/api/modules/nixio.README.html
index a8da0f36da..d8a17f78b4 100644
--- a/documentation/api/modules/nixio.README.html
+++ b/documentation/api/modules/nixio.README.html
@@ -288,7 +288,7 @@
  <br />In general all functions are namend and behave like their POSIX API 
  counterparts - where applicable - applying the following rules: 
  <ul> 
- <li>Functions should be named like the underlying POSIX API function ommiting 
+ <li>Functions should be named like the underlying POSIX API function omitting
  prefixes or suffixes - especially when placed in an object-context ( 
  lockf -> File:lock, fsync -> File:sync, dup2 -> dup, ...)</li> 
  <li>If you are unclear about the behaviour of a function you should consult 
@@ -296,10 +296,10 @@
  <li>If the name is significantly different from the POSIX-function, the 
  underlying function(s) are stated in the documentation.</li> 
  <li>Parameters should reflect those of the C-API, buffer length arguments and  
- by-reference parameters should be ommitted for pratical purposes.</li> 
+ by-reference parameters should be omitted for pratical purposes.</li>
  <li>If a C function accepts a bitfield as parameter, it should be translated 
  into lower case string flags representing the flags if the bitfield is the  
- last parameter and also ommiting prefixes or suffixes. (e.g.  waitpid 
+ last parameter and also omitting prefixes or suffixes. (e.g.  waitpid
  (pid, &s, WNOHANG | WUNTRACED) -> waitpid(pid, "nohang", "untraced"),  
  getsockopt(fd, SOL_SOCKET, SO_REUSEADDR, &opt, sizeof(opt)) -> 
  Socket:getopt("socket", "reuseaddr"), etc.) </li>