Fixed typos

docs/websockets/echo-server.html

@@ -220,9 +220,9 @@ <h2 class="heading-2"><span class="blue-text">Step 2:</span> Setting up the Serv
 }
 </code></pre>
       <p class="block-text">The <strong>HeliumLogger</strong> is set up to log info, warning, and error type messages.</p>
-      <p class="block-text">The <strong>ChatService</strong> defined in the <strong>ChatService.swift</strong> file is registered on the path chat.</p>
-      <p class="block-text">An <strong>HTTP server</strong> is created and setup to listen on port 8080.</p>
-      <p class="block-text">With this server set up clients should connect to the chat service as ws://host:8080/chat, where hostis the host running the server.</p>
+      <p class="block-text">The ChatService defined in the <strong>ChatService.swift</strong> file is registered on the path chat.</p>
+      <p class="block-text">An HTTP server is created and setup to listen on port 8080.</p>
+      <p class="block-text">With this server set up clients should connect to the chat service as ws://host:8080/chat, where host is the host running the server.</p>
       <h2 class="heading-2"><span class="blue-text">Step 3:</span> Setting up the Client</h2>
       <p class="block-text">The client has a simple command line interface. At startup one passes the host and port number. The client simply reads messages to be sent from the terminal and displays messages received on the terminal as well.</p>
       <p class="block-text">To create a new directory for the client, exit out of your server directory and run this terminal command:</p>

docs/websockets/websockets.html

@@ -108,7 +108,7 @@ <h1 class="docs-title"><a href="/index.html">KITURA <span class="blue-text">DOCS
     <div id="doc-container" class="docs-item-4 docs-window">
       <main>
         <h1 class="heading-1">What are WebSockets?</h1>
-        <p class="block-text">In the early days of the web, a client and server relationship was viewed as following a single direction of workflow, the client would send a request to the server and the server would respond to the client with the data requested.  However, as time progressed, this relationship evolved into one that became idirectional, with both the client and server sending and receiving data to and from each other.</p>
+        <p class="block-text">In the early days of the web, a client and server relationship was viewed as following a single direction of workflow, the client would send a request to the server and the server would respond to the client with the data requested.  However, as time progressed, this relationship evolved into one that became bidirectional, with both the client and server sending and receiving data to and from each other.</p>
         <p class="block-text">WebSockets were created as a way of providing a low latency persistent connection that is bidirectional between a client and a server.  They are low latency as there is no need to send lots of headers that typical HTTP requests consist of.  A WebSocket connection is created with a WebSocket handshake, this involves the client sending an initial HTTP request including an Upgrade' header to which, if the server supports the protocol, it agrees with the request and sends back its own 'Upgrade' header in response.  After a successful handshake, the established connection uses the WebSocket protocol 'ws'.</p>
         <div class="option img">
           <img src="../../assets/websocket.png" alt="">