Fix some typos

- add = signs between command line flags and values in artifact files
- fix relative paths linking to artifacts in cli-reference.md

Signed-off-by: Brian Woodward <brian.woodward@gmail.com>

artifacts/server.yaml

@@ -21,8 +21,7 @@ spec:
         args:
         - "server"
         - "--auto-tls=true"
-        - "--remote-tcp 127.0.0.1"
-        - "--common-name PUBLIC_IP_GOES_HERE"
+        - "--remote-tcp=127.0.0.1"
+        - "--common-name=PUBLIC_IP_GOES_HERE"
         - "--token=AUTHTOKENHERE"
 ---
-

artifacts/split-plane-server.yaml

@@ -21,8 +21,8 @@ spec:
         args:
         - "server"
         - "--auto-tls=true"
-        - "--remote-tcp 127.0.0.1"
-        - "--common-name PUBLIC_IP_GOES_HERE"
+        - "--remote-tcp=127.0.0.1"
+        - "--common-name=PUBLIC_IP_GOES_HERE"
         - "--token=AUTHTOKENHERE"
 ---
 
@@ -45,7 +45,7 @@ spec:
   selector:
     app: inlets-server
 
-# Public LoadBalancer, or Ingress, or NodePort to which the remote service 
+# Public LoadBalancer, or Ingress, or NodePort to which the remote service
 # behind NAT or a firewall will connect
 
 # If we are tunnelling `ssh` for instance on port 22

docs/cli-reference.md

@@ -208,11 +208,11 @@ You can deploy an inlets-server in one of three ways:
 
     This configuration is ideal for command and control. The private network will be able to traverse firewalls and NAT to connect to the remote inlets-pro server, but only internal services within the Kubernetes cluster can connect to the tunnelled service.
 
-    See [split-plane-server.yaml](artifacts/split-plane-server.yaml) as an example.
+    See [split-plane-server.yaml](../artifacts/split-plane-server.yaml) as an example.
 
 ### Pod / Service / Deployment definitions
 
-You can use the sample artifact for the [client.yaml](artifacts/client.yaml) or [server.yaml](artifacts/server.yaml)
+You can use the sample artifact for the [client.yaml](../artifacts/client.yaml) or [server.yaml](../artifacts/server.yaml)
 
 ### Common issues
 
@@ -256,7 +256,7 @@ You can use the sample artifact for the [client.yaml](artifacts/client.yaml) or
 * Multiple inlets tunnels
 
     You can run as many inlets tunnels as you like, both client and server Pods. Make sure that each is named appropriately.
-    
+
     The server will require its own Service and Deployment.
 
     The client just requires a Deployment.