Bump @types/node to latest release of v15 (#1296)

* Bump @types/node to latest release of v14

* Bump major version to v15

website/content/docs/getting-started/connect-to-target.mdx

@@ -112,11 +112,11 @@ command arguments, and these values are additionally injected as environment
 variables in the executed command:
 
 - `{{boundary.ip}}` (`BOUNDARY_PROXIED_IP`): The IP address of the listening
-socket that `boundary connect` has opened.
+  socket that `boundary connect` has opened.
 - `{{boundary.port}}` (`BOUNDARY_PROXIED_PORT`): The port of the listening
-socket that `boundary connect` has opened.
+  socket that `boundary connect` has opened.
 - `{{boundary.addr}}` (`BOUNDARY_PROXIED_ADDR`): The host:port format of the
-address. This is essentially equivalent to `{{boundary.ip}}:{{boundary.port}}`.
+  address. This is essentially equivalent to `{{boundary.ip}}:{{boundary.port}}`.
 
 For example, if you wanted to use Boundary to create an authenticated firewall
 around 'curl', you could update the default TCP target from a default port