Browse Source

spelling: service

Josh Soref 7 years ago
parent
commit
86ebc57b2e
3 changed files with 3 additions and 3 deletions
  1. 1 1
      doc/guide/shell.xml
  2. 1 1
      src/lib/process/io_service_signal.cc
  3. 1 1
      src/lib/process/libprocess.dox

+ 1 - 1
doc/guide/shell.xml

@@ -53,7 +53,7 @@ kea-shell [--host hostname] [--port number] [--timeout seconds] [--service servi
 
       <listitem>
         <simpara>
-          <command>--service <replaceable>serive-name</replaceable></command> specifies the
+          <command>--service <replaceable>service-name</replaceable></command> specifies the
           target of a command. If not given, CA will be used as target.  May be used more
           than once to specify multiple targets.
         </simpara>

+ 1 - 1
src/lib/process/io_service_signal.cc

@@ -60,7 +60,7 @@ IOSignal::TimerCallback::operator()() {
 IOSignalQueue::IOSignalQueue(asiolink::IOServicePtr& io_service)
     : io_service_(io_service), signals_() {
     if (!io_service_) {
-        isc_throw(IOSignalError, "IOSignalQueue - io_serivce cannot be NULL");
+        isc_throw(IOSignalError, "IOSignalQueue - io_service cannot be NULL");
     }
 }
 

+ 1 - 1
src/lib/process/libprocess.dox

@@ -103,7 +103,7 @@ isc::asiolink::IOService::run() or its variants.  These calls are not
 interrupted upon signal receipt as is the select() function and while
 boost::asio provides a signal mechanism it requires linking in additional
 libraries.  Therefore, CPL provides its own signal handling mechanism to
-propagate an OS signal such as SIGHUP to an IOSerivce as a ready event with a
+propagate an OS signal such as SIGHUP to an IOService as a ready event with a
 callback.
 
 isc::process::DControllerBase uses two mechanisms to carry out signal handling.  It