Typo fixes (#5661)

* Typo fixes
* it's -> its
* plugable -> pluggable

website/source/api/nodes.html.md

@@ -930,7 +930,7 @@ $ curl \
 
   - `Message` - The specific message for the event, detailing what occurred.
 
-  - `Subsystem` - The subsystem where the node event took place. Subsysystems
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
     include:
 
     - `Drain` - The Nomad server draining subsystem.

website/source/api/search.html.md

@@ -32,7 +32,7 @@ job related results will not be returned. If the token is only valid for
 
 ### Parameters
 
-- `Prefix` `(string: <required>)` - Specifies the identifer against which
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
   matches will be found. For example, if the given prefix were "a", potential
   matches might be "abcd", or "aabb".
 - `Context` `(string: <required>)` - Defines the scope in which a search for a

website/source/docs/internals/plugins/base.html.md

@@ -33,7 +33,7 @@ PluginInfoResponse{
 
 #### `ConfigSchema() (*hclspec.Spec, error)`
 
-The `ConfigSchema` function allows a plugin to tell Nomad the schema for it's
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
 configuration. This configuration is given in a [plugin block][pluginblock] of
 the client configuration. The schema is defined with the [hclspec][hclspec]
 package.

website/source/docs/internals/plugins/index.html.md

@@ -13,7 +13,7 @@ functionality of some components within Nomad. The design of the plugin system
 is inspired by the lessons learned from plugin systems implemented in other
 HashiCorp products such as Terraform and Vault.
 
-The following components are currently plugable within Nomad:
+The following components are currently pluggable within Nomad:
 
 - [Task Drivers](/docs/internals/plugins/task-drivers.html)
 - [Devices](/docs/internals/plugins/devices.html)

website/source/docs/internals/plugins/task-drivers.html.md

@@ -16,7 +16,7 @@ driver source][lxcdriver].
 
 Authoring a task driver (shortened to driver in this documentation) in Nomad
 consists of implementing the [DriverPlugin][driverplugin] interface and adding
-a main package to launch the plugin. A driver plugin is long lived and it's
+a main package to launch the plugin. A driver plugin is long lived and its
 lifetime is not bound to the Nomad client. This means that the Nomad client can
 be restarted without the restarting the driver. Nomad will ensure that one
 instance of the driver is running, meaning if the driver crashes or otherwise

website/source/docs/job-specification/artifact.html.md

@@ -92,7 +92,7 @@ artifact {
 }
 ```
 
-To download from private repo, sshkey need to be set. The key must be
+To download from private repo, sshkey needs to be set. The key must be
 base64-encoded string. Run `base64 -w0 <file>`
 
 ```hcl

website/source/docs/job-specification/parameterized.html.md

@@ -32,7 +32,7 @@ To invoke a parameterized job, [`nomad job
 dispatch`][dispatch command] or the equivalent HTTP APIs are
 used. When dispatching against a parameterized job, an opaque payload and
 metadata may be injected into the job. These inputs to the parameterized job act
-like arguments to a function. The job consumes them to change it's behavior,
+like arguments to a function. The job consumes them to change its behavior,
 without exposing the implementation details to the caller.
 
 To that end, tasks within the job can add a

website/source/docs/job-specification/service.html.md

@@ -513,7 +513,7 @@ directly since Nomad isn't managing any port assignments.
 ### IPv6 Docker containers
 
 The [Docker](/docs/drivers/docker.html#advertise_ipv6_address) driver supports the
-`advertise_ipv6_address` parameter in it's configuration.
+`advertise_ipv6_address` parameter in its configuration.
 
 Services will automatically advertise the IPv6 address when `advertise_ipv6_address` 
 is used.

website/source/guides/security/acl.html.markdown

@@ -406,7 +406,7 @@ authentication backends, it could provide a workflow where a user or orchestrati
 using an pre-existing identity service (LDAP, Okta, Amazon IAM, etc.) in order to obtain a short-lived
 Nomad token.
 
-~> HashiCorp Vault is a standalone product with it's own set of deployment and
+~> HashiCorp Vault is a standalone product with its own set of deployment and
    configuration best practices. Please review [Vault's
    documentation](https://www.vaultproject.io/docs/index.html) before deploying it
    in production.