Use placeholder for user name to avoid confusion

lectures/command-line/slides.qmd

@@ -106,7 +106,7 @@ Different ways to work on a cluster depending on the task:
 
 * Connect to the login nodes via secure shell (`ssh`)
   ```{raw}
-  ssh a123456@levante.dkrz.de
+  ssh <YOUR_USERNAME>@levante.dkrz.de
   ```
   (use your user id instead of a123456)
 * Now you have access to the command line on levante
@@ -124,7 +124,7 @@ Different ways to work on a cluster depending on the task:
 * Upload the public (`.pub`) key to your [DKRZ profile](https://luv.dkrz.de) ([instructions](https://docs.dkrz.de/doc/levante/access-and-environment.html)), so levante can check your connection attempts
 * Use your private ssh key instead of your password when connecting to levante
   ```bash
-  ssh -i ~/.ssh/id_ed25519_levante a123456@levante.dkrz.de
+  ssh -i ~/.ssh/id_ed25519_levante <YOUR_USERNAME>@levante.dkrz.de
   ```
 
 ## Configuring SSH
@@ -133,7 +133,7 @@ Different ways to work on a cluster depending on the task:
   ```{.sshconfig filename=~/.ssh/config}
   Host levante # the name you use in the shell
      Hostname levante.dkrz.de # the official name of the system
-     User a123456 # your user id
+     User <YOUR_USERNAME> # add your user id
      IdentityFile ~/.ssh/id_ed25519_levante # your private key
   ```
   (call `man ssh_config` for more info)
@@ -150,11 +150,11 @@ Different ways to work on a cluster depending on the task:
 * There are different tools to transfer between your local machine and a remote server
 * For single files, a simple `scp` is sufficient
   ```{raw}
-  scp a123456@levante.dkrz.de:file_in_home .
+  scp <YOUR_USERNAME>@levante.dkrz.de:file_in_home .
   ```
 * `rsync` is a more powerful alternative
   ```{raw}
-  rsync a123456@levante.dkrz.de:file_in_home .
+  rsync <YOUR_USERNAME>@levante.dkrz.de:file_in_home .
   ```
 
 ## Remote file transfer {auto-animate=true visibility="uncounted"}