fix typos

dietpi/Odroid_HC1_HC2.md

@@ -5,7 +5,7 @@
 ![](pictures/DroidBlitz.jpg)
 
 ## There are 3 options provided:
-* a trusted SDcard image 
+* a trusted fully prebuilt SDcard image
 * building your own SDcard from an updated DietPi image.
 * Build your own SDcard from the image downloaded from [Dietpi.com](dietpi.com#download)
 ---
@@ -30,7 +30,7 @@ The setup continues with the [RaspiBlitz Setup Process](https://github.com/rootz
 ---
 ### Download the updated DietPi image
 
-* For the Odroid HC1 / HC2 / XU3 / XU4 a v6.20.6 DietPi image with fail2ban installed is uploaded [here](
+For the Odroid HC1 / HC2 / XU3 / XU4 a v6.20.6 DietPi image with fail2ban installed is uploaded [here](
 https://mega.nz/#!AcdVBAbR!O-W3jP5LUgw7lMY8S9XcBWcKX3IhRNAAFmaYzDXIUC0).  
 sha256sum DietPi_v6.20.6_OdroidXU4-ARMv7-Stretch.img: 
 1459b91f66b9db98f3437c31231e44497b7b7dcd9146d2cc41a3da653f9a9215
@@ -39,13 +39,13 @@ sha256sum DietPi_v6.20.6_OdroidXU4-ARMv7-Stretch.img:
 
 * Insert the SDcard into the Odroid.
 
-* Power up and continue with: [Run the RaspiBlitz build_sdcard.sh script](#Run-the-RaspiBlitz-build_sdcard.sh-script)
+* Power up and continue with [running the RaspiBlitz build_sdcard.sh script](#Run-the-RaspiBlitz-build_sdcard.sh-script)
 
 ---
 
 ### Build your own DietPi image:
 
-* Watch out this is an ardous process. 
+Watch out this is an ardous process. 
 Updating from a v6.14 DietPi image is causing a bootloop under some circumstances. Will be sorted once the current, >6.2 version is uploaded for the Odroids.  
 
 * For the Odroid HC1 / HC2 / XU3 / XU4 the start is this image:   
@@ -65,7 +65,7 @@ automatic apt update & apt upgrade and asks to reboot
 * Log back in:
 `ssh root@[IP-OF-DIETPI]`  
 password: `dietpi`  
-* after the previous update the ssh keys might change:
+* after the update the ssh keys might change:
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@  
 @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @  
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@  
@@ -75,8 +75,8 @@ run (can be copied from the terminal output):
 yes >   
 password: `dietpi`  
 
-* At this point if the DietPi was not updated from 6.14 it does not manage to save settings going forward.  
-Exit the sotware installer (press Tab to jump to Exit)
+* At this point if the DietPi OS was not updated from 6.14 it does not manage to save settings going forward.  
+Exit the software installer (press Tab to jump to Exit)
 ![](pictures/dietpi-software_exit.png)  
 
 * in the bash prompt run:  
@@ -88,17 +88,18 @@ Reboots
 * Log back in:  
 `ssh root@[IP-OF-DIETPI]`  
 password: `dietpi` 
-* In the DietPi software menu install fail2ban and make OpenSSH server the default SSH server.
-Changing the SSH server will change the SSH keys again. To clear:  
-`ssh-keygen -f "/home/[your-linux-username]/.ssh/known_hosts" -R "dietpi.IP"`  
+* In the DietPi software menu install fail2ban and make OpenSSH server the default SSH server.  
 Ok > Cancel > Cancel  
 Search `fail2ban` > Space to select > Enter  
 SSH server > switch from Dropbear to the OpenSSH-server  
 Install > Ok  
 Opt out of survey > Ok  
 Reboots again
 
-* Changing the SSH server will change the SSH keys again. To clear:  
+* Log back in:  
+`ssh root@[IP-OF-DIETPI]`  
+password: `dietpi`  
+Changing the SSH server will change the SSH keys again. To clear:  
 `ssh-keygen -f "/home/[your-linux-username]/.ssh/known_hosts" -R "dietpi.IP"`
 
 

dietpi/README.md

@@ -20,6 +20,8 @@ See the [hardware comparison](hw_comparison.md).
 
 ### Setting up the DietPi OS
 
+Getting started with DietPi: https://dietpi.com/phpbb/viewtopic.php?f=8&t=9#p9 
+
 * Start with an ARM based Single Board Computer listed on DietPi.com.  
 At least 1GB RAM is recommended.  
 Look for the SD card image for the specific SBC in the [download section](https://dietpi.com/#download).
@@ -32,18 +34,14 @@ Look for the SD card image for the specific SBC in the [download section](https:
 A USB 2.0 port will not be able to power an HDD so you will need extra cable
 If you are connecting the HDD to a USB 3.0 port and have an at least 2A power supply, you might be able to run without an extra cable.
 
-* Power up and continue with: [Run the DietPi optimized Raspiblitz SDcard build script](#Run-the-RaspiBlitz-build_sdcard.sh-script)
-
-
-
-* In the desktop terminal on Linux / MacOS or Putty on Windows:  
+* Power up and log in with the desktop terminal on Linux / MacOS or Putty on Windows:  
 `ssh root@[IP-OF-DIETPI]`  
 password: `dietpi`  
-Getting started with DietPi: https://dietpi.com/phpbb/viewtopic.php?f=8&t=9#p9 
 
-* You might be asked about updating DietPi. This might not be straightforward if starting froma  version <6.20. Try to update, it is best to build on the latest version.
 
-* In the DietPi software menu install fail2ban and make OpenSSH server the default SSH server.
+* You might be asked about updating DietPi. This is not a straightforward process if starting from a  version <6.20. Try to update, it is best to build on the latest version.
+
+* In the DietPi software menu install `fail2ban` and make `OpenSSH server` the default SSH server.  
 Changing the SSH server will change the SSH keys again. To clear:  
 `ssh-keygen -f "/home/[your-linux-username]/.ssh/known_hosts" -R "dietpi.IP"`
 
@@ -57,13 +55,13 @@ password: `dietpi`
 
 ### Run the RaspiBlitz build_sdcard.sh script
 
-* Format of the command to build the SDcard:  
+* Use this format to build the SDcard with the Raspiblitz script:  
 `wget https://raw.githubusercontent.com/[GITHUB-USERNAME]/raspiblitz/[BRANCH]/build_sdcard.sh && sudo bash build_sdcard.sh [BRANCH] [GITHUB-USERNAME]`  
 If you are working from a forked repo be aware of that the fork needs to be called `raspiblitz` for the git downloads to work.
 
 * Run the forked version of @openoms:  
 `wget https://raw.githubusercontent.com/openoms/raspiblitz/raspiblitz-dev/build_sdcard.sh && sudo bash build_sdcard.sh raspiblitz-dev openoms`  
-This will take a couple minutes depending on your internet ceonnection and the processing power of the SBC.
+This will take a couple minutes depending on your internet connection and the processing power of the SBC.
 
 * Restart when done and log back in now as `admin`:  
 `ssh admin@[IP-OF-DROIDBLITZ]`