docs: update dev docs

docs/c_development.md

@@ -152,6 +152,13 @@ aws ec2 run-instances \
 
 Step 2: SSH into your new EC2 instance and configure it with the following:
 
+- SSH: Find your instance's public IP. This may be in the output of your `run-instance` command, if not search for your instance id in the AWS web console and under the details copy your public ipv4 address. Example below assumes this value is `1.2.3.4`, replace that with the actual value.
+
+```bash
+YOURPUBLICEC2IP=1.2.3.4
+ssh -i $AWSUSERNAME.pem ubuntu@$YOURPUBLICEC2IP
+```
+
 - Install Docker CE
 
 ```bash
@@ -199,13 +206,15 @@ k3d cluster create -s 1 -a 3 -v /etc/machine-id:/etc/machine-id  --k3s-server-ar
 # Create the directory for the k3s registry config.
 mkdir ~/.k3d/
 
-# Create the config file. Use your registry1 credentials. Copy your user name and token secret from your Harbor profile.
+# Create the config file. Use your registry1 credentials. 
+# To get those go to Harbor (https://registry1.dso.mil/) and login via OIDC (using your P1 login).
+# From the top right menu access your user profile and the username and CLI secret will be there.
 cat << EOF > ~/.k3d/p1-registries.yaml
 configs:
   "registry1.dso.mil":
     auth:
       username: "user.name"
-      password: "place_token_secret_here"
+      password: "cli.secret"
 EOF
 
 YOURPUBLICEC2IP=$( curl https://ipinfo.io/ip )
@@ -244,7 +253,7 @@ Update the configuration file on your local workstation.
 rm ~/.kube/config
 
 # Create empty configuation
-touch ~/kube/config
+touch ~/.kube/config
 
 # Update permissions
 # (Prevents Helm warnings)
@@ -254,7 +263,7 @@ chmod go-r ~/.kube/config
 vi ~/.kube/config
 ```
 
-Paste the contents into the new file, and update the `server` URL to the public IP address (`$YOURPUBLICEC2IP`).
+Paste the contents into the new file, and update the `server` URL to the public IP address (`$YOURPUBLICEC2IP`). Leave the port untouched.
 
 ```bash
 # Test to see if you can connect to your cluster