clarification on Day 0 requirements and matching wording between versions

Author: livialima

docs/00-AWS-Free-Tier.md

@@ -9,7 +9,10 @@ Refer to [Day 0 - Get Your Own Server](https://linuxupskillchallenge.org/00) to
 * [In the Cloud (with providers like DigitalOcean, Linode and Vultr)](https://linuxupskillchallenge.org/00-VPS-small)
 * [In the Cloud (with providers like AWS, Azure and Google Cloud)](https://linuxupskillchallenge.org/00-VPS-big)
 
+**TIP**: check out the walk-though in the [complementary video](https://www.youtube.com/live/_-6UYOjRIVQ?t=2892s). This video covers a lot of possible setups (local server with VirtualBox, AWS, Digital Ocean, Azure, Linode, Google Cloud, Vultr and Oracle Cloud).
+
 ## AWS free-tier, is it always free?
+
 The AWS Free Tier is designed to allow new users to explore and test various AWS services without incurring any costs for 12 months following the AWS sign-up date, subject to certain usage limits. When your 12 month free usage term expires or if your application use exceeds the tiers, you simply pay standard, pay-as-you-go service rates. You can extend that free usage with an Educate Pack, if you are eligible.
 
 ## Signing up with AWS Educate pack:
@@ -52,27 +55,37 @@ Your server instance should now launch, and you can login to it by:
 
 ## Remote access via SSH
 
-You should see an "IPv4" entry for your server, this is its unique Internet IP address, and is how you'll connect to it via SSH (the Secure Shell protocol) - something we'll be covering in the first lesson.
+You should see a "Public IPv4 address" (or similar) entry for your server in the account's control panel, this is its unique Internet IP address, and it is how you'll connect to it via SSH (the Secure Shell protocol) - something we'll be covering in the first lesson.
 
 This video, [How to Set Up AWS EC2 and Connect to Linux Instance with PuTTY](https://www.youtube.com/watch?v=kARWT4ETcCs), gives a good overview of the process.
 
-You will be logging in as the user *ubuntu*. It has been added to the 'adm' and 'sudo' groups, which on an Ubuntu system gives it access to read various logs - and to "become root" as required via the _sudo_ command.
+You will be logging in as the user `ubuntu`. It has been added to the `adm` and `sudo` groups, which on an Ubuntu system gives it access to read various logs - and to "become root" as required via the _sudo_ command.
 
 ## You are now a sysadmin
 
 Confirm that you can do administrative tasks by typing:
 
-`sudo apt update`
+```bash
+sudo apt update
+```
 
-(Normally you'd expect this would prompt you to confirm your password, but because you're using public key authentication the system hasn't prompted you to set up a password - and AWS have configured *sudo* to not request one for "ubuntu").
+(Normally you'd expect this would prompt you to confirm your password, but because you're using public key authentication the system hasn't prompted you to set up a password - and AWS have configured `sudo` to not request one for `ubuntu`).
 
 Then:
 
-`sudo apt upgrade`
+```bash
+sudo apt upgrade -y
+```
 
 Don't worry too much about the output and messages from these commands, but it should be clear whether they succeeded or not. (Reply to any prompts by taking the default option). These commands are how you force the installation of updates on an Ubuntu Linux system, and only an administrator can do them.
 
-To logout, type _logout_ or _exit_.
+**REBOOT**
+
+When a kernel update is identified in this first check for updates, the system might ask the user to reboot. This is one of the few occasions you will need to reboot your server, so go for it after the update is done:
+
+```bash
+sudo reboot now
+```
 
 Your server is now all set up and ready for the course!
 
@@ -82,4 +95,12 @@ Note that:
 * You alone are responsible for managing it
 * You have just installed the latest updates, so it should be secure for now
 
+To logout, type `logout` or `exit`.
+
+## When you are done
+
+You should be safe running the VM during the month for the challenge, but you can **Stop** the instance at any point. It will continue to count towards the bill, though.
+
+When you no longer need the VM, **Terminate/Destroy** instance.
+
 **Now you are ready to start the challenge. [Day 1](https://linuxupskillchallenge.org/01), here we go!**

docs/00-Azure-Free-Tier.md

@@ -9,6 +9,8 @@ Refer to [Day 0 - Get Your Own Server](https://linuxupskillchallenge.org/00) to
 * [In the Cloud (with providers like DigitalOcean, Linode and Vultr)](https://linuxupskillchallenge.org/00-VPS-small)
 * [In the Cloud (with providers like AWS, Azure and Google Cloud)](https://linuxupskillchallenge.org/00-VPS-big)
 
+**TIP**: check out the walk-though in the [complementary video](https://www.youtube.com/live/_-6UYOjRIVQ?t=7020s). This video covers a lot of possible setups (local server with VirtualBox, AWS, Digital Ocean, Azure, Linode, Google Cloud, Vultr and Oracle Cloud).
+
 ## Signing up with Azure
 
 Sign-up is fairly simple - just provide your email address and a password of your choosing - along with a phone number for a 2FA - a second method of authentication. Azure can be a bit funny about 'corporate' email addresses, eg using a work address or your own domain. Create a new @outlook or @gmail.com account if so using the link on the sign-up page.
@@ -44,23 +46,33 @@ This opens all ports and protocols to access from anywhere. While this might be
 
 Ensure your machine is 'running' (if not, click 'start') and connect using the 'connect -> ssh' dropdown and following instructions
 
-You will be logging in as the user *azureuser*. It has been added to the 'adm' and 'sudo' groups, which on an Ubuntu system gives it access to read various logs - and to "become root" as required via the _sudo_ command.
+You will be logging in as the user `azureuser`. It has been added to the `adm` and `sudo` groups, which on an Ubuntu system gives it access to read various logs - and to "become root" as required via the _sudo_ command.
 
 ## You are now a sysadmin
 
 Confirm that you can do administrative tasks by typing:
 
-`sudo apt update`
+```bash
+sudo apt update
+```
 
-(Normally you'd expect this would prompt you to confirm your password, but because you're using public key authentication the system hasn't prompted you to set up a password - and Azure have configured *sudo* to not request one for "azureuser").
+(Normally you'd expect this would prompt you to confirm your password, but because you're using public key authentication the system hasn't prompted you to set up a password - and Azure have configured `sudo` to not request one for `azureuser`).
 
 Then:
 
-`sudo apt upgrade`
+```bash
+sudo apt upgrade -y
+```
 
 Don't worry too much about the output and messages from these commands, but it should be clear whether they succeeded or not. (Reply to any prompts by taking the default option). These commands are how you force the installation of updates on an Ubuntu Linux system, and only an administrator can do them.
 
-To logout, type _logout_ or _exit_.
+**REBOOT**
+
+When a kernel update is identified in this first check for updates, the system might ask the user to reboot. This is one of the few occasions you will need to reboot your server, so go for it after the update is done:
+
+```bash
+sudo reboot now
+```
 
 Your server is now all set up and ready for the course!
 
@@ -70,4 +82,12 @@ Note that:
 * You alone are responsible for managing it
 * You have just installed the latest updates, so it should be secure for now
 
+To logout, type `logout` or `exit`.
+
+## When you are done
+
+You should be safe running the VM during the month for the challenge, but you can **Stop** the instance at any point. It will continue to count towards the bill, though.
+
+When you no longer need the VM, **Terminate/Destroy** instance.
+
 **Now you are ready to start the challenge. [Day 1](https://linuxupskillchallenge.org/01), here we go!**

docs/00-Google-Cloud.md

@@ -9,6 +9,8 @@ Refer to [Day 0 - Get Your Own Server](https://linuxupskillchallenge.org/00) to
 * [In the Cloud (with providers like DigitalOcean, Linode and Vultr)](https://linuxupskillchallenge.org/00-VPS-small)
 * [In the Cloud (with providers like AWS, Azure and Google Cloud)](https://linuxupskillchallenge.org/00-VPS-big)
 
+**TIP**: check out the walk-though in the [complementary video](https://www.youtube.com/live/_-6UYOjRIVQ?t=8778s). This video covers a lot of possible setups (local server with VirtualBox, AWS, Digital Ocean, Azure, Linode, Google Cloud, Vultr and Oracle Cloud).
+
 ## Signing up with GCP
 
 Sign-up is fairly simple - just provide your email address and a password of your choosing - along with a phone number for a 2FA - a second method of authentication.
@@ -33,25 +35,35 @@ Create and repeat the steps by creating a new Firewall and setting "Direction of
 
 ## Logging in for the first time
 
-Select your instance and click "ssh" it will open a new window console. To access the root, type "sudo -i passwd" in the command line then set your own password. Log in by typing "su" and "password". Note that the password won't show as you type or paste it.
+Select your instance and click "SSH", it will open a new window console. To access the root, type `sudo -i passwd` in the command line then set your own password. Log in by typing `su` and then your password. Note that the password won't show as you type or paste it.
 
-## Setting up SSH
+## Remote access via SSH
 
 You can also refer to <https://cloud.google.com/compute/docs/instances/connecting-advanced#thirdpartytools> if you intend to access your server via third-party tools (e.g. Putty).
 
 ## You are now a sysadmin
 
 Confirm that you can do administrative tasks by typing:
 
-`sudo apt update`
+```bash
+sudo apt update
+```
 
 Then:
 
-`sudo apt upgrade`
+```bash
+sudo apt upgrade -y
+```
 
 Don't worry too much about the output and messages from these commands, but it should be clear whether they succeeded or not. (Reply to any prompts by taking the default option). These commands are how you force the installation of updates on an Ubuntu Linux system, and only an administrator can do them.
 
-To logout, type _logout_ or _exit_.
+**REBOOT**
+
+When a kernel update is identified in this first check for updates, the system might ask the user to reboot. This is one of the few occasions you will need to reboot your server, so go for it after the update is done:
+
+```bash
+sudo reboot now
+```
 
 Your server is now all set up and ready for the course!
 
@@ -61,4 +73,12 @@ Note that:
 * You alone are responsible for managing it
 * You have just installed the latest updates, so it should be secure for now
 
+To logout, type `logout` or `exit`.
+
+## When you are done
+
+You should be safe running the VM during the month for the challenge, but you can **Stop** the instance at any point. It will continue to count towards the bill, though.
+
+When you no longer need the VM, **Terminate/Destroy** instance.
+
 **Now you are ready to start the challenge. [Day 1](https://linuxupskillchallenge.org/01), here we go!**

docs/00-Local-Server.md

@@ -9,6 +9,8 @@ Refer to [Day 0 - Get Your Own Server](https://linuxupskillchallenge.org/00) to
 * [In the Cloud (with providers like DigitalOcean, Linode and Vultr)](https://linuxupskillchallenge.org/00-VPS-small)
 * [In the Cloud (with providers like AWS, Azure and Google Cloud)](https://linuxupskillchallenge.org/00-VPS-big)
 
+**TIP**: check out the walk-though in the [complementary video](https://www.youtube.com/live/_-6UYOjRIVQ?t=643s). This video covers a lot of possible setups (local server with VirtualBox, AWS, Digital Ocean, Azure, Linode, Google Cloud, Vultr and Oracle Cloud).
+
 ## It's difficult to create a server in cloud without a credit card
 
 We normally recommend using Amazon's AWS "Free Tier" or Digital Ocean - but both require that you have a credit card. The same is true of the Microsoft Azure, Google's GCP and the vast majority of providers listed at Low End Box (<https://lowendbox.com/>).
@@ -27,7 +29,7 @@ Some will accept PayPal, or Bitcoin - but typically those who don't have a credi
 
 You can run the challenge on a home server and all the commands will work as they would on a cloud server. However, not being exposed to the wild certainly loses the feel of what real sysadmins have to face.
 
-If you set your own VM at a private server, go for the minimum requirements like 1GHz CPU core, 1GB RAM, and a couple of gigs of disk space. You can always adapt this to your heart's desire (or how much hardware you have available).
+If you set your own VM at a private server, go for the minimum requirements like 1GHz CPU core, 1GB RAM, and 5GB of disk space. You can always adapt this to your heart's desire (or how much hardware you have available).
 
 Our recommendation is: use a cloud server if you can, to get the full experience, but don't get limited by it. **This is your server.**
 
@@ -50,7 +52,7 @@ Install [VirtualBox](https://www.virtualbox.org/), when ready:
 * **Finish** but we're not done yet.
 * The new VM should show up in a list of VMs, select it.
 * Click on *Machine > Settings*
-* Click on *Storage*. Right-click on Controllet IDE, click on *Optical Drive*.
+* Click on *Storage*. Right-click on Controller IDE, click on *Optical Drive*.
 * Select the Linux ISO you downloaded from the list if available, if not click *Add* and find it in your directories. Click *Choose*.
 * Click on *Network* and change the network adapter to **Bridged Adapter**.
 * Click *OK*
@@ -80,11 +82,13 @@ Use **arrow keys** and the **enter key** to select options. When you're ok with
 
 After the first reboot, it will show a black screen asking for the `login`. That's when you use that username and password you created during the install.
 
-Note: the password will not show up, not even `***`, just trust that is taking it in.
+Note: the password will not show up, not even `******`, just trust that is taking it in.
 
 If you need to find out the IP address for the VM, just type in the console:
 
-`ip address`
+```bash
+ip address
+```
 
 That will give you the `inet`, i.e., the ip address. You will need that to connect with SSH.
 
@@ -94,33 +98,43 @@ If you are using Windows 10 or 11, follow the instructions to [connect using the
 
 If you are on Linux or MacOS, open a terminal and run the command:
 
-`ssh username@ip_address`
+```bash
+ssh username@ip_address
+```
 
-Or, using the SSH private key, `ssh -i private_key username@ip_address`
+Or, using the SSH private key:
 
-Enter your password (or a passphrase, if your SSH key is protected with one)
+```bash
+ssh -i private_key username@ip_address
+```
 
-Voila! You have just accessed your server remotely.
+Enter your password (or a passphrase, if your SSH key is protected with one)
 
-If in doubt, consult the [complementary video](https://youtube.com/live/_-6UYOjRIVQ) that covers a lot of possible setups (local server with VirtualBox, AWS, Digital Ocean, Azure, Linode, Google Cloud, Vultr and Oracle Cloud).
+Voilà! You have just accessed your server remotely.
 
 ## You are now a sysadmin
 
 Confirm that you can do administrative tasks by typing:
 
-`sudo apt update`
+```bash
+sudo apt update
+```
 
 Then:
 
-`sudo apt upgrade -y`
+```bash
+sudo apt upgrade -y
+```
 
 Don't worry too much about the output and messages from these commands, but it should be clear whether they succeeded or not. (Reply to any prompts by taking the default option). These commands are how you force the installation of updates on an Ubuntu Linux system, and only an administrator can do them.
 
 **REBOOT**
 
-When a kernel update is identified in this first check for updates, this is one of the few occasions you will need to reboot your server, so go for it after the update is done:
+When a kernel update is identified in this first check for updates, the system might ask the user to reboot. This is one of the few occasions you will need to reboot your server, so go for it after the update is done:
 
-`sudo reboot now`
+```bash
+sudo reboot now
+```
 
 Your server is now all set up and ready for the course!
 
@@ -132,9 +146,11 @@ To logout, type `logout` or `exit`.
 
 ## When you are done
 
-Just type:
+To shutdown your server while you're not using it, just type:
 
-`sudo shutdown now`
+```bash
+sudo shutdown now
+```
 
 Or click on _Force Shutdown_