res

Author: urban-adeininger

docs/developer/concepts/seq_num.html

@@ -2602,7 +2602,7 @@ <h1 id="sequence-numbers"><a name="sequence-numbers" class="plugin-anchor" href=
 <li>If possible, receivers should be able to ask for missing messages by id</li>
 </ul>
 <p>With NATS you can embed sequence ids in the message or include them as a token in the subject. For example, a sender can send messages to <code>updates.1</code>, <code>updates.2</code>, etc... and the subscribers can listen to <code>updates.*</code> and parse the subject to determine the sequence id.
-Placing a sequence token into the subject may be desireable if the payload is unknown or embedding additional data such as a sequence number in the payload is not possible.</p>
+Placing a sequence token into the subject may be desirable if the payload is unknown or embedding additional data such as a sequence number in the payload is not possible.</p>
 
 
                                 </section>

docs/developer/events/slow.html

@@ -2830,7 +2830,7 @@ <h2 id="detect-a-slow-consumer-and-check-for-dropped-messages"><a name="detect-a
 
        <span class="token keyword">if</span> <span class="token builtin">len</span><span class="token punctuation">(</span>msgs<span class="token punctuation">)</span> <span class="token operator">==</span> <span class="token number">3</span><span class="token punctuation">:</span>
          <span class="token comment"># Head of line blocking on other messages caused</span>
-	 <span class="token comment"># by single message proccesing taking long...</span>
+	 <span class="token comment"># by single message processing taking long...</span>
          <span class="token keyword">await</span> asyncio<span class="token punctuation">.</span>sleep<span class="token punctuation">(</span><span class="token number">1</span><span class="token punctuation">)</span>
 
    <span class="token keyword">await</span> nc<span class="token punctuation">.</span>subscribe<span class="token punctuation">(</span><span class="token string">&quot;updates&quot;</span><span class="token punctuation">,</span> cb<span class="token operator">=</span>cb<span class="token punctuation">,</span> pending_msgs_limit<span class="token operator">=</span><span class="token number">5</span><span class="token punctuation">)</span>

docs/developer/streaming/protocol.html

@@ -2739,7 +2739,7 @@ <h5 id="message-structure"><a name="message-structure" class="plugin-anchor" hre
 <p><a href="#protocols">Back to table</a></p>
 <h4 id="unsubscriberequest"><a name="unsubscriberequest" class="plugin-anchor" href="#unsubscriberequest"><i class="fa fa-link" aria-hidden="true"></i></a>UnsubscribeRequest</h4>
 <h5 id="description"><a name="description" class="plugin-anchor" href="#description"><i class="fa fa-link" aria-hidden="true"></i></a>Description</h5>
-<p>The <code>UnsubscribeRequest</code> closes or unsubcribes the subscription from the specified subject. The inbox specified is the <code>inbox</code> returned from the NATS Streaming Server in the <code>SubscriptionResponse</code>. Depending on which subject this request is sent, the action will result in close (if sent to subject <code>subCloseRequests</code>) or unsubscribe (if sent to subject <code>unsubRequests</code>)</p>
+<p>The <code>UnsubscribeRequest</code> closes or unsubsprecribes the subscription from the specified subject. The inbox specified is the <code>inbox</code> returned from the NATS Streaming Server in the <code>SubscriptionResponse</code>. Depending on which subject this request is sent, the action will result in close (if sent to subject <code>subCloseRequests</code>) or unsubscribe (if sent to subject <code>unsubRequests</code>)</p>
 <h5 id="message-structure"><a name="message-structure" class="plugin-anchor" href="#message-structure"><i class="fa fa-link" aria-hidden="true"></i></a>Message Structure</h5>
 <ul>
 <li><code>clientID</code>: Client ID originally provided in the <a href="#connectrequest">ConnectRequest</a></li>

docs/gateways/gateway.html

@@ -2652,7 +2652,7 @@ <h3 id="gateway-configuration-block"><a name="gateway-configuration-block" class
 </tr>
 <tr>
 <td style="text-align:left"><code>host</code></td>
-<td style="text-align:left">Interface where the gateway will listen for incomming gateway connections.</td>
+<td style="text-align:left">Interface where the gateway will listen for incoming gateway connections.</td>
 </tr>
 <tr>
 <td style="text-align:left"><code>listen</code></td>
@@ -2664,7 +2664,7 @@ <h3 id="gateway-configuration-block"><a name="gateway-configuration-block" class
 </tr>
 <tr>
 <td style="text-align:left"><code>port</code></td>
-<td style="text-align:left">Port where the gateway will listen for incomming gateway connections.</td>
+<td style="text-align:left">Port where the gateway will listen for incoming gateway connections.</td>
 </tr>
 <tr>
 <td style="text-align:left"><code>reject_unknown</code></td>

docs/nats_protocol/nats-protocol.html

@@ -2758,7 +2758,7 @@ <h4 id="example"><a name="example" class="plugin-anchor" href="#example"><i clas
 <p><code>SUB BAR G1 44\r\n</code></p>
 <h2 id="unsub"><a name="unsub" class="plugin-anchor" href="#unsub"><i class="fa fa-link" aria-hidden="true"></i></a>UNSUB</h2>
 <h4 id="description"><a name="description" class="plugin-anchor" href="#description"><i class="fa fa-link" aria-hidden="true"></i></a>Description</h4>
-<p><code>UNSUB</code> unsubcribes the connection from the  specified subject, or auto-unsubscribes after the specified number of messages has been received.</p>
+<p><code>UNSUB</code> unsubscribes the connection from the  specified subject, or auto-unsubscribes after the specified number of messages has been received.</p>
 <h4 id="syntax"><a name="syntax" class="plugin-anchor" href="#syntax"><i class="fa fa-link" aria-hidden="true"></i></a>Syntax</h4>
 <p><code>UNSUB <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>sid</span><span class="token punctuation">&gt;</span></span> [max_msgs]</code></p>
 <p>where:</p>

docs/nats_protocol/nats-server-protocol.html

@@ -2685,7 +2685,7 @@ <h4 id="example"><a name="example" class="plugin-anchor" href="#example"><i clas
 <h2 id="rs"><a name="rs" class="plugin-anchor" href="#rs"><i class="fa fa-link" aria-hidden="true"></i></a><a name="SUB"></a>RS+</h2>
 <h4 id="description"><a name="description" class="plugin-anchor" href="#description"><i class="fa fa-link" aria-hidden="true"></i></a>Description</h4>
 <p><code>RS+</code> initiates a subscription to a subject on on a given account, optionally with a distributed queue group name and weighting factor.
-Note that queue subscriptions will use RS+ for increases and descreases to queue weight except when the weighting factor is 0.</p>
+Note that queue subscriptions will use RS+ for increases and decreases to queue weight except when the weighting factor is 0.</p>
 <h4 id="syntax"><a name="syntax" class="plugin-anchor" href="#syntax"><i class="fa fa-link" aria-hidden="true"></i></a>Syntax</h4>
 <p><strong>Subscription</strong>: <code>RS+ <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>account</span><span class="token punctuation">&gt;</span></span> <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>subject</span><span class="token punctuation">&gt;</span></span>\r\n</code></p>
 <p><strong>Queue Subscription</strong>: <code>RS+ <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>account</span><span class="token punctuation">&gt;</span></span> <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>subject</span><span class="token punctuation">&gt;</span></span> <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>queue</span><span class="token punctuation">&gt;</span></span> <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>weight</span><span class="token punctuation">&gt;</span></span>\r\n</code></p>
@@ -2698,7 +2698,7 @@ <h4 id="syntax"><a name="syntax" class="plugin-anchor" href="#syntax"><i class="
 </ul>
 <h2 id="rs-"><a name="rs-" class="plugin-anchor" href="#rs-"><i class="fa fa-link" aria-hidden="true"></i></a><a name="UNSUB"></a>RS-</h2>
 <h4 id="description"><a name="description" class="plugin-anchor" href="#description"><i class="fa fa-link" aria-hidden="true"></i></a>Description</h4>
-<p><code>RS-</code> unsubcribes from the specified subject on the given account. It is sent by a server when it no longer has interest in a given subject.</p>
+<p><code>RS-</code> unsubscribes from the specified subject on the given account. It is sent by a server when it no longer has interest in a given subject.</p>
 <h4 id="syntax"><a name="syntax" class="plugin-anchor" href="#syntax"><i class="fa fa-link" aria-hidden="true"></i></a>Syntax</h4>
 <p><strong>Subscription</strong>: <code>RS- <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>account</span><span class="token punctuation">&gt;</span></span> <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>subject</span><span class="token punctuation">&gt;</span></span>\r\n</code></p>
 <p>where:</p>

docs/nats_server/clients.html

@@ -2610,7 +2610,7 @@ <h3 id="testing-your-setup"><a name="testing-your-setup" class="plugin-anchor" h
 [29785] 2019/05/16 08:46:13.467206 [TRC] 127.0.0.1:49805 - cid:1 - -&gt;&gt; [PONG]
 </code></pre><p>If you had created a subscriber, you should notice output on the subscriber telling you that it disconnected, and reconnected. The server output above is more interesting. You can see the subscriber send a <code>CONNECT</code> protocol message and a <code>PING</code> which was responded to by the server with a <code>PONG</code>.</p>
 <blockquote>
-<p>You  can learn more about the <a href="../nats_protocol/nats-protocol.html">NATS protocol here</a>, but more intersting than the protocol description is <a href="../nats_protocol/nats-protocol-demo.html">an interactive demo</a>.</p>
+<p>You  can learn more about the <a href="../nats_protocol/nats-protocol.html">NATS protocol here</a>, but more interesting than the protocol description is <a href="../nats_protocol/nats-protocol-demo.html">an interactive demo</a>.</p>
 </blockquote>
 <p>On a third terminal, publish your first message:</p>
 <pre class="language-"><code>&gt; nats-pub hello world

docs/nats_streaming/configuring/cmdline.html

@@ -2624,7 +2624,7 @@ <h1 id="command-line-arguments"><a name="command-line-arguments" class="plugin-a
     -sl,  --signal <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>signal</span><span class="token punctuation">&gt;</span></span>[=<span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>pid</span><span class="token punctuation">&gt;</span></span>]      Send signal to nats-streaming-server process (stop, quit, reopen)
           --encrypt <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>bool</span><span class="token punctuation">&gt;</span></span>               Specify if server should use encryption at rest
           --encryption_cipher <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>string</span><span class="token punctuation">&gt;</span></span>   Cipher to use for encryption. Currently support AES and CHAHA (ChaChaPoly). Defaults to AES
-          --encryption_key <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>sting</span><span class="token punctuation">&gt;</span></span>       Encryption Key. It is recommended to specify it through the NATS_STREAMING_ENCRYPTION_KEY environment variable instead
+          --encryption_key <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>string</span><span class="token punctuation">&gt;</span></span>       Encryption Key. It is recommended to specify it through the NATS_STREAMING_ENCRYPTION_KEY environment variable instead
 
 Streaming Server Clustering Options:
     --clustered <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span>bool</span><span class="token punctuation">&gt;</span></span>                   Run the server in a clustered configuration (default: false)

docs/nats_streaming/gettingstarted/changes.html

@@ -2631,7 +2631,7 @@ <h2 id="version-060"><a name="version-060" class="plugin-anchor" href="#version-
 <ul>
 <li>Added error <code>ErrAlreadyExists</code> that <code>CreateChannel()</code> should return if channel already exists.</li>
 <li><code>RecoveredState</code> has now <code>Channels</code> (instead of <code>Subs</code>) and is a map of <code>*RecoveredChannel</code> keyed by channel name.</li>
-<li><code>RecoveredChannel</code> has a pointer to a <code>Channel</code> (formely <code>ChannelStore</code>) and an array of pointers to <code>RecoveredSubscription</code> objects.</li>
+<li><code>RecoveredChannel</code> has a pointer to a <code>Channel</code> (formerly <code>ChannelStore</code>) and an array of pointers to <code>RecoveredSubscription</code> objects.</li>
 <li><code>RecoveredSubscription</code> replaces <code>RecoveredSubState</code>.</li>
 <li><code>Client</code> no longer stores a <code>UserData</code> field.</li>
 <li><code>Channel</code> (formerly <code>ChannelStore</code>) no longer stores a <code>UserData</code> field.</li>

docs/nats_tools/nas/nas_conf.html

@@ -2710,7 +2710,7 @@ <h4 id="store-configuration"><a name="store-configuration" class="plugin-anchor"
 </tr>
 <tr>
 <td style="text-align:left"><code>nsc</code></td>
-<td style="text-align:left">Configures an nsc read-only store. The value should be the path to an operator <em>directory</em>. Option is mutually exlusive with <code>dir</code>.</td>
+<td style="text-align:left">Configures an nsc read-only store. The value should be the path to an operator <em>directory</em>. Option is mutually exclusive with <code>dir</code>.</td>
 </tr>
 <tr>
 <td style="text-align:left"><code>readonly</code></td>