Correction of command syntax

content/documentation/PinePhone/Installation/Installation_to_the_eMMC.md

@@ -18,7 +18,7 @@ The internal memory of the PinePhone (eMMC) can be flashed using multiple differ
 2. Insert microSD card and boot the phone
 3. Download the desired OS' image on the booted OS or transfer it to the microSD card
 4. Extract the image file if it is archived
-5. Flash the image file to eMMC using `dd if=**IMAGE.img** of=/dev/**mmcblkX** bs=1M status=progress conv=fsync` where X is the number label of the eMMC (of the disk, not the partition!). Use the command `lsblk` to check your devices: typically with the current kernel the microSD card is _/dev/mmcblk0_ and the eMMC is _/dev/mmcblk2_ but as always with _dd_ be extremely cautious to get the devices correct.
+5. Flash the image file to eMMC using `dd if=IMAGE.img of=/dev/mmcblkX bs=1M status=progress conv=fsync` where X is the number label of the eMMC (of the disk, not the partition!). Use the command `lsblk` to check your devices: typically with the current kernel the microSD card is _/dev/mmcblk0_ and the eMMC is _/dev/mmcblk2_ but as always with _dd_ be extremely cautious to get the devices correct.
 6. Turn off phone, remove microSD card and then turn on the phone.
 
 ## Using JumpDrive

content/documentation/PinePhone/Installation/Installation_to_the_microSD_card.md

@@ -58,7 +58,7 @@ For flashing the microSD card, the command _dd_ can be used as well.
 
 Make sure to select the correct device using `lsblk`. Then run _dd_ with the selected device:
 
-`sudo dd if=**IMAGE.img** of=/dev/**[DEVICE]** bs=1M status=progress conv=fsync`
+`sudo dd if=IMAGE.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync`
 
 {{< admonition type="note" >}}
  The image needs to be written to the whole device, not to partition 1. Make sure you’re NOT selecting _/dev/sda1_ or _/dev/mmcblk0p1_ as target.
@@ -70,7 +70,7 @@ Make sure to select the correct device using `lsblk`. Then run bmaptool with the
 
 Download the _IMAGE.xz_ and the _IMAGE.bmap_ files, then run:
 
-`bmaptool copy --bmap **IMAGE.bmap** **IMAGE.xz** /dev/**[DEVICE]**`
+`bmaptool copy --bmap IMAGE.bmap IMAGE.xz /dev/[DEVICE]`
 
 This takes around 2.5 minutes to flash a 4 Gb file.
 

content/documentation/PinePhone/Installation/Reuse_microSD_card.md

@@ -19,10 +19,10 @@ This can be done as follows on any Linux system:
 to check the device of your microSD card – as an example lets assume it is /dev/mmcblk0
 then
 
-`sudo dd if=/dev/zero of=/dev/**[DEVICE]** bs=8k seek=1 count=4`
+`sudo dd if=/dev/zero of=/dev/[DEVICE] bs=8k seek=1 count=4`
 
 will clear the relevant sectors of your card.
 
 Since Danctnix (arch) switched to a gpt partition table from mbr in May of 2022 it installs u-boot at an offset of 128k instead of 8k, which means this command must be used instead
 
-`sudo dd if=/dev/zero of=/dev/**[DEVICE]** bs=32k seek=4 count=1`
+`sudo dd if=/dev/zero of=/dev/[DEVICE] bs=32k seek=4 count=1`

content/documentation/PinePhone_Pro/Software/Installation_instructions.md

@@ -28,8 +28,8 @@ To install an image to the microSD card:
 1. Download a compatible image from [Releases](/documentation/PinePhone_Pro/Software/Releases).
 2. **Important:** Typically the image will be compressed in an archive file to reduce the download size (such as _.gz_ or _.xz_). Extract the image from its archive file to get the file with the file extension _.img_.
 3. Write the image to your microSD card using your favorite method, examples:
-   * Using _dd_: On the device you’re flashing the microSD card from, find the correct device under `lsblk` and then flash the image to the microSD card using `sudo dd if=**IMAGE.img** of=/dev/**[DEVICE]** bs=1M status=progress conv=fsync` and make sure the target is the whole microSD card and not its first partition, _sdc1_ or _mmcblk0p1_ are wrong!
-   * Using _bmaptool_: Make sure to select the correct device using `lsblk`. Then run bmaptool with the correct device: Download the _IMAGE.xz_ and the _IMAGE.bmap_ files, then run `bmaptool copy --bmap **IMAGE.bmap** **IMAGE.xz** /dev/**[DEVICE]**`. This takes around 2.5 minutes to flash a 4 GB file.
+   * Using _dd_: On the device you’re flashing the microSD card from, find the correct device under `lsblk` and then flash the image to the microSD card using `sudo dd if=IMAGE.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync` and make sure the target is the whole microSD card and not its first partition, _sdc1_ or _mmcblk0p1_ are wrong!
+   * Using _bmaptool_: Make sure to select the correct device using `lsblk`. Then run bmaptool with the correct device: Download the _IMAGE.xz_ and the _IMAGE.bmap_ files, then run `bmaptool copy --bmap IMAGE.bmap IMAGE.xz /dev/[DEVICE]`. This takes around 2.5 minutes to flash a 4 GB file.
    * Using _a graphical tool_: A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
 4. Insert the microSD card into the top slot of the PinePhone Pro
 5. Boot the device using the following method:
@@ -56,7 +56,7 @@ This installation method is **recommended**.
 2. Download or copy the desired image to the microSD card as file
 3. Check if the eMMC appears under `lsblk`. If it doesn’t appear in the output of the command, the eMMC wasn’t initialized due to applying the above explained bypass method for a too long time during the boot
 4. **Important:** Typically the image will be compressed in an archive file to reduce the download size (such as _.gz_ or _.xz_). Extract the image from its archive file to get the file with the file extension _.img_.
-5. Flash the image file using `sudo dd if=**IMAGE.img** of=/dev/mmcblk2 bs=1M status=progress conv=fsync` (replace _IMAGE.img_ with the filename of the image you want to flash and make sure it has the file extension _.img_).
+5. Flash the image file using `sudo dd if=IMAGE.img of=/dev/mmcblk2 bs=1M status=progress conv=fsync` (replace _IMAGE.img_ with the filename of the image you want to flash and make sure it has the file extension _.img_).
 6. Reboot the PinePhone Pro
 
 ### By using Tow-Boot
@@ -74,7 +74,7 @@ This installation method is **not recommended**, as the USB connection can be un
 `mmcblk2      179:0    0 115.2G  0 disk`\
 `├─mmcblk2p1  179:1    0   122M  0 part /boot`\
 `└─mmcblk2p2  179:2    0 115.1G  0 part /`\
-Note: In this example, ***dev/mmcblk2*** is the device, while _mmcblk2p1_ and _mmcblk2p2_ are partitions of the device. The downloaded images are images from full devices, which means that the full device (_mmcblk2_ in this example) needs to be flashed. Ignore the partitions!
+Note: In this example, **/dev/mmcblk2** is the device, while _mmcblk2p1_ and _mmcblk2p2_ are partitions of the device. The downloaded images are images from full devices, which means that the full device (_mmcblk2_ in this example) needs to be flashed. Ignore the partitions!
 7. **Important:** Typically the image will be compressed in an archive file to reduce the download size (such as _.gz_ or _.xz_). Extract the image from its archive file to get the file with the file extension _.img_
-8. Flash the image file using `sudo dd if=**IMAGE.img** of=/dev/**DEVICE** bs=1M status=progress conv=fsync` (replace _IMAGE.img_ with the filename of the image you want to flash and make sure it has the file extension _.img_ and replace _DEVICE_ with the correct device from the _lsblk_ command)
+8. Flash the image file using `sudo dd if=IMAGE.img of=/dev/DEVICE bs=1M status=progress conv=fsync` (replace _IMAGE.img_ with the filename of the image you want to flash and make sure it has the file extension _.img_ and replace _DEVICE_ with the correct device from the _lsblk_ command)
 9. Reboot the PinePhone Pro

content/documentation/PinePhone_Pro/Software/Multi-distribution_image.md

@@ -405,7 +405,7 @@ Any time a distribution update rebuilds the initramfs it is necessary to delete
 
 In case you want to reinstall only one distribution, the easy way is to delete and recreate the selected partition using the GParted GUI.
 
-If the device doesn’t start, connect a compatible [serial cable](https://pine64.com/product/pinebook-pinephone-pinetab-serial-console) to the headphone jack and a computer, switch off microswitch 6 and start a serial console to investigate further. Find out the corresponding USB device using `ls /dev/ttyUSB*` and then connect to it with for example _minicom_ using the command `minicom -b 1500000 -D /dev/ttyUSB***[...]****`, where *[...]** is the number of the USB device.
+If the device doesn’t start, connect a compatible [serial cable](https://pine64.com/product/pinebook-pinephone-pinetab-serial-console) to the headphone jack and a computer, switch off microswitch 6 and start a serial console to investigate further. Find out the corresponding USB device using `ls /dev/ttyUSB*` and then connect to it with for example _minicom_ using the command `minicom -b 1500000 -D /dev/ttyUSB[...]`, where **[...]** is the number of the USB device.
 
 To find the exact _LABEL_, _UUID_, _PARTLABEL_ and _PARTUUID_ names, open a terminal window on the phone and use the command `blkid`.
 

content/documentation/PineTab2/Software/Installation_instructions.md

@@ -26,8 +26,8 @@ Graphical applications:
 
 Command-line tools:
 
-* **cp**: `sudo cp **IMAGE.img** /dev/**[DEVICE]**`
-* **dd**: `sudo dd if=**IMAGE.img** of=/dev/**[DEVICE]** bs=1M status=progress conv=fsync`
+* **cp**: `sudo cp IMAGE.img /dev/[DEVICE]`
+* **dd**: `sudo dd if=IMAGE.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync`
 
 {{< admonition type="note" >}}
  Make sure to replace **IMAGE.img** and **[DEVICE]** with the filename of the image (double check if it is decompressed and has the file extension _.img_) and the device name. You can use the command `lsblk` to find the device name. Make sure to flash to the whole device instead of partition 1 and that you’re NOT selecting _/dev/sda1_ or _/dev/mmcblk0p1_ as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.

content/documentation/Pinecil/Further_information/Specifications.md

@@ -53,7 +53,7 @@ menu:
 
 ![Thumb Screws](/documentation/images/Pinecil-Thumb-Screws-02.png)
 
-* Originals screws are Phillips ([source](https://www.reddit.com/r/PINE64official/comments/tatf5l/comment/ig4r92v/?context=3)): two M2x3mm at the front, and one M2x4mm is the ground screw near the `**[-]**` minus button.
+* Originals screws are Phillips ([source](https://www.reddit.com/r/PINE64official/comments/tatf5l/comment/ig4r92v/?context=3)): two M2x3mm at the front, and one M2x4mm is the ground screw near the **[-]** minus button.
 * The bottom-front screw only holds the handle together and does not touch the tip, hence is a shorter m2x 3mm.
 * _Thumb screws_ are popular upgrades: an _M2 x 4mm_ thumb screw could replace both the front screen-side Tip holder screw and the ground screw in the rear of the handle.
 * It was found that an M2x3mm thumb screw for the tip is a hair _too short_, and just grazes the Tip and the longer _m2 x 4mm is better on top_.

content/documentation/Pinecil/Usage.md

@@ -32,18 +32,18 @@ Do not try to bend the two [internal contacts](https://pine64.com/product/pineci
 
 **3. Heat the tip**: plug Pinecil into an appropriate [power supply](/documentation/Pinecil/Power_supplies/Power_supplies).
 
-1. Clicking `**[+]**` starts the tip heating.
+1. Clicking **[+]** starts the tip heating.
 2. The detailed display option shows power draw, current temperature, supply voltage, and time until sleep mode starts.
-3. Adjust the target temperature with further clicks of `**[+]**` and `**[-]**` buttons.
-4. Wait a few seconds for the regular display to return, then hold down `**[-]**` for a moment to turn the heat off.
+3. Adjust the target temperature with further clicks of **[+]** and **[-]** buttons.
+4. Wait a few seconds for the regular display to return, then hold down **[-]** for a moment to turn the heat off.
 5. You can observe the temperature measurement go up and down. Certain settings involve holding down both buttons (see [GitHub IronOS for details on firmware](https://ralim.github.io/IronOS/) settings).
 
 **4. Using the Settings Menu**:
 
-1. To check the firmware version, hold down the `**[-]**` button. It will display something like "v2.19.A3BBABC 13-07-22". This is the firmware number and release date, the date is July 13, 2022 in the example.
-2. Clicking `**[-]**` when heat is off steps through main categories menus to control a variety of settings, see [Getting started with menus section](/documentation/Pinecil/Usage/#getting_started_with_the_menu).
-3. Clicking `**[-]**` also returns to the regular display of temperature and supply voltage (this view varies if you activate detailed idle). At other times it may show power draw.
-4. Click `**[-]**` to scroll to the the main menu section desired (i.e., User Interface). Then click `**[+]**` button to change various internal settings. Then click `**[-]**` again to go to the next item in the sub-menu.
+1. To check the firmware version, hold down the **[-]** button. It will display something like "v2.19.A3BBABC 13-07-22". This is the firmware number and release date, the date is July 13, 2022 in the example.
+2. Clicking **[-]** when heat is off steps through main categories menus to control a variety of settings, see [Getting started with menus section](/documentation/Pinecil/Usage/#getting_started_with_the_menu).
+3. Clicking **[-]** also returns to the regular display of temperature and supply voltage (this view varies if you activate detailed idle). At other times it may show power draw.
+4. Click **[-]** to scroll to the the main menu section desired (i.e., User Interface). Then click **[+]** button to change various internal settings. Then click **[-]** again to go to the next item in the sub-menu.
 
 **5. Important notes**:
 

content/documentation/ROCK64/Software/Releases.adoc

@@ -315,7 +315,7 @@ Flashing the distribution to the eMMC:
 * Copy the image file to micro SD by using SFTP. The image file must have the _.img_ file extension.
 * After finish copy the file, power off the board and add eMMC module to the board
 * Boot the board, run below command for flashing to eMMC module
-* Run `sudo dd if=*[IMAGE]* of=/dev/*[DEVICE]* bs=10M` (example: _sudo dd if=slack-current-aarch64-xfce_08May18-4.4.126-rock64-build-20180508.img of=/dev/mmcblk1 bs=10M_).
+* Run `sudo dd if=[IMAGE] of=/dev/[DEVICE] bs=10M` (example: _sudo dd if=slack-current-aarch64-xfce_08May18-4.4.126-rock64-build-20180508.img of=/dev/mmcblk1 bs=10M_).
 * then edit these two files in eMMC module:
 ** `mount /dev/mmcblk1p1 /media`
 ** `echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt`

content/documentation/ROCKPro64/Software/Releases.adoc

@@ -322,7 +322,7 @@ The following creates a bootable image from an existing Void Linux installation:
 ** create a rootfs via _mkrootfs.sh_: `sh mkrootfs.sh -o void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz`
 ** `sh mkplatformfs.sh rockpro64 void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz`
 ** `sh mkimage.sh -s 7GiB void-rockpro64-PLATFORMFS-yyyymmdd.tar.xz`
-* write image to sdcard or eMMC: `dd if=*IMAGE-FILENAME* of=*DEVICENAME* bs=2M`
+* write image to sdcard or eMMC: `dd if=IMAGE-FILENAME of=DEVICENAME bs=2M`
 * If _mkplatformfs.sh_ errors with _ROCKPro64 not supported_, install _xbps-src_ from https://github.com/void-linux/void-packages and build the ROCKPro64 package.
 * Tip:  write a new U-Boot to the image if you see on the serial console the boot-up stalls:
 ** get the two U-Boot files from https://pkgs.org/download/u-boot-rockpro64[pkgs.org], the aarch64 files: