fix(tuto): chef2

Author: ldecarvalho-doc

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

@@ -24,7 +24,7 @@ You can easily manage up to 10,000 nodes using Chef. Chef also makes it easy to
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
-- One of the following remote machines running Ubuntu (this tutorial was validated for machines running Ubuntu Xenial or Ubuntu Focal Fossa):
+- One of the following remote machines running Ubuntu (this tutorial was validated for machines running Ubuntu 24.04 or previous:
     - An [Instance](/instances/how-to/create-an-instance/)
     - An [Elastic Metal server](/elastic-metal/how-to/create-server/)
     - A [Dedibox dedicated server](/dedibox/how-to/order-a-server/)
@@ -307,18 +307,18 @@ This is done through a `knife.rb` file that we will place in the `~/chef_repo/.c
     log_location             STDOUT
     node_name                "name_for_workstation"
     client_key               "#{current_dir}/name_of_user_key"
-    validation_client_name   "organization_validator_name"
+    validation_client_name   "organization-validator"
     validation_key           "#{current_dir}/organization_validator_key"
     chef_server_url          "https://server_domain_or_public_IP/organizations/organization_name"
     syntax_check_cache_path  "#{ENV['HOME']}/.chef/syntaxcache"
     cookbook_path            ["#{current_dir}/../cookbooks"]
     ```
 
-    - **node_name:** Specifies the name that knife will use to connect to your Chef server. This should match your username.
-    - **client_key:** Name and path to the user key that you copied over from the Chef server. We can use the `#{current_dir}` snippet to fill in the path if the key is in the same directory as the `knife.rb` file.
-    - **validation_client_name:** Name of the validation client that knife will use to bootstrap new nodes. This will take the form of your organization short name, followed by `-validator`.
-    - **validation_key:** Like the `client_key`, this includes the name and path to the validation key you copied from the Chef server. Again, you can use the `#{current_dir}`.
-    - **chef_server_url:** This is the URL where the Chef server can be reached. It should begin with `https://`, followed by your Chef server's domain name or **Public IP address**. Afterward, the path to your organization should be specified by appending /organizations/your_organization_name.
+    - `node_name` - Specifies the name that knife will use to connect to your Chef server. This should match your username.
+    - `client_key` - Name and path to the user key that you copied over from the Chef server. We can use the `#{current_dir}` snippet to fill in the path if the key is in the same directory as the `knife.rb` file.
+    - `validation_client_name` - Name of the validation client that knife will use to bootstrap new nodes. This will take the form of your organization short name, followed by `-validator`.
+    - `validation_key` - Like the `client_key`, this includes the name and path to the validation key you copied from the Chef server. Again, you can use the `#{current_dir}`.
+    - `chef_server_url` - This is the URL where the Chef server can be reached. It should begin with `https://`, followed by your Chef server's domain name or **Public IP address**. Afterward, the path to your organization should be specified by appending /organizations/your_organization_name.
 
     For our tutorial, the file looks like this: