Typo fixes (#5661)

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

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