content: fix typos, update nats URL

src/app/homepage/pages/microservices/grpc/grpc.component.html

@@ -21,7 +21,7 @@ <h4>Transporter</h4>
   </blockquote>
   <h4>Options</h4>
   <p>
-    There is a bunch of available options that determine a transporter behavior.
+    There are a bunch of available options that determine a transporter behavior.
   </p>
   <table>
     <tr>

src/app/homepage/pages/microservices/mqtt/mqtt.component.html

@@ -18,7 +18,7 @@ <h4>Overview</h4>
   <pre><code class="language-typescript">{{ options }}</code></pre>
   <h4>Options</h4>
   <p>
-    There is a bunch of available options that determine a transporter behavior.
+    There are a bunch of available options that determine a transporter behavior.
     They are well-described <a href="https://github.com/mqttjs/MQTT.js" target="blank">here</a>.
   </p>
 </div>

src/app/homepage/pages/microservices/nats/nats.component.html

@@ -1,7 +1,7 @@
 <div class="content">
   <h3>NATS</h3>
   <p>
-    The <a href="http://mqtt.org/" target="blank">NATS</a> is a simple, high performance open source messaging system.
+    The <a href="https://nats.io" target="blank">NATS</a> is a simple, high performance open source messaging system.
   </p>
   <h4>Installation</h4>
   <p>Before we start, we have to install required package:</p>
@@ -18,7 +18,7 @@ <h4>Overview</h4>
   <pre><code class="language-typescript">{{ options }}</code></pre>
   <h4>Options</h4>
   <p>
-    There is a bunch of available options that determine a transporter behavior.
+    There are a bunch of available options that determine a transporter behavior.
     They are well-described <a href="https://github.com/nats-io/node-nats#connect-options" target="blank">here</a>.
   </p>
 </div>

src/app/homepage/pages/microservices/redis/redis.component.html

@@ -20,7 +20,7 @@ <h4>Overview</h4>
   <pre><code class="language-typescript">{{ options }}</code></pre>
   <h4>Options</h4>
   <p>
-    There is a bunch of available options that determine a transporter behaviour.
+    There are a bunch of available options that determine a transporter behaviour.
   </p>
   <table>
     <tr>

src/app/homepage/pages/techniques/authentication/authentication.component.html

@@ -2,7 +2,7 @@
   <h3>Authentication</h3>
   <p>
     Authentication is an
-    <strong>essential</strong> part of most existing applications. There is a lot of different approaches, strategies, and ways to
+    <strong>essential</strong> part of most existing applications. There are a lot of different approaches, strategies, and ways to
     handle user authorization. What we eventually decide to use depends on the particular application requirements and is
     strongly associated with their needs.
   </p>

src/app/homepage/pages/websockets/gateways/gateways.component.html

@@ -37,7 +37,7 @@ <h4>Basics</h4>
   <pre [class.hide]="subscribeEventsT.isJsActive"><code class="language-typescript">{{ subscribeEvents }}</code></pre>
   <pre [class.hide]="!subscribeEventsT.isJsActive"><code class="language-typescript">{{ subscribeEventsJs }}</code></pre>
   <blockquote class="info">
-    <strong>Hint</strong> The <code>WsResponse</code> interface is imported from <code>@nestjs/common</code> package, while <code>@SubscribeMessage()</code> decorator from <code>@nestjs/websockets</code>.
+    <strong>Hint</strong> Both <code>WsResponse</code> interface and <code>@SubscribeMessage()</code> decorator are imported from <code>@nestjs/common</code> package.
   </blockquote>
   <p>
     The <code>onEvent()</code> function takes 2 arguments. First one is a library-specific <a href="https://socket.io/docs/server-api/#socket" target="blank">socket instance</a> and the second one is the data received from the client.