fix(tuto): chef

Author: ldecarvalho-doc

tutorials/configure-chef-ubuntu-xenial/index.mdx

@@ -9,7 +9,7 @@ tags: Chef Ubuntu Xenial Focal-Fossa
 categories:
   - instances
 dates:
-  validation: 2024-10-28
+  validation: 2025-05-14
   posted: 2018-07-05
 ---
 
@@ -130,28 +130,29 @@ Creating an admin user enables a specific user to make changes to the infrastruc
 
   For our example, we will create a user with the following information:
 
-    - **Username:** testuser
-    - **First Name:** test
-    - **Last Name:** user
-    - **Email:** [email protected]
-    - **Password:** pwdexample
-    - **Filename:** testuser.pem
+    - `USERNAME` - `testuser`
+    - `FIRST_NAME` - `test`
+    - `LAST_NAME` - `user`
+    - `EMAIL` - `[email protected]`
+    - `PASSWORD` - `pwdexample`
+    - `FILENAME` - `testuser.pem`
 
-  We will also add `-f` option to specify a filename in which to output our new user's private RSA key. We will need this to authenticate using the `knife` management command later. In the end, the command translates to:
+  We will also add `-f` option to specify a `FILENAME` in which to output our new user's private RSA key. We will need this to authenticate using the `knife` management command later. In the end, the command translates to:
 
   ```
   chef-server-ctl user-create testuser test user [email protected] pwdexample -f testuser.pem
   ```
 2. Launch the `chef-server-ctl` with the `org-create` subcommand:
     ```
-    chef-server-ctl org-create SHORTNAME LONGNAME --association_user USERNAME
+    chef-server-ctl org-create SHORTNAME LONGNAME --association_user ADMIN_USERNAME FILENAME
     ```
 
     For our example, we will create an organization with the following information:
-      - **Short Name** (refers to the organization within Chef): scaleway
-      - **Long Name** (name of the organization): Scaleway, Inc.
-      - **Association User** (username that has access to administer the organization): testuser
-      - **Filename:** scaleway-file.pem
+
+      - `SHORT_NAME` - Refers to the organization within Chef. In this example we use `scaleway`
+      - `LONG_NAME` - The name of the organization. In this example, `Scaleway, Inc`
+      - `ADMIN_USERNAME` - The username of a user with administration rights on the organization. In this example, `testuser`
+      - `FILENAME` - `scaleway-file.pem`
 
     Again, we will add the `-f` flag to specify the private key file location. The key that will be created is used to validate new clients as part of the organization until they can get their own unique client key. In the end, the command translates to:
 
@@ -218,18 +219,18 @@ The method that you use to connect to the Chef server will determine how to down
 
 #### Option 1: (Recommended) Downloading keys when connecting to a Chef server using SSH keys
 
-1. Leave your workstation
+1. Leave your workstation.
     ```
     exit
     ```
 
-  The next steps should be carried out from the machine that holds the private SSH key needed to connect to your Chef server.
+    The next steps should be carried out from the machine that holds the private SSH key needed to connect to your Chef server.
 2. Add the SSH key you use to connect to the Chef server to an SSH agent:
     ```
     eval $(ssh-agent)
     ```
 
-    which should start the agent and return something similar to
+    Which should start the agent and return something similar to:
 
     ```
     Agent pid 2893