fix: color

Author: Patrick M

_posts/2022-12-18-debian-lxc-setup.md

@@ -80,7 +80,7 @@ patrick ALL=(ALL) NOPASSWD: ALL
 ```
 
 > Once you've made the changes, you can restart the LXC and use SSH with your new user
-> {: .prompt-tip }
+{: .prompt-tip }
 
 ## Unattended Upgrades Configuration
 

_posts/2022-12-18-install-pihole-ha.md

@@ -115,7 +115,7 @@ vrrp_instance pihole {
 | 8    | The other nodes IPs                                                                                                                                                                                                                                                                      |
 
 > Never set an IP reservation for the virtual IP, or set it as a static address for another device
-> {: .prompt-warning }
+{: .prompt-warning }
 
 Also keep in mind, this is set up for unicast, but can be configured for multicast. I just like to be explicit. You can find more details about [keepalived configuration here](https://keepalived.readthedocs.io/en/latest/configuration_synopsis.html).
 

_posts/2022-12-18-lxc-plex-setup.md

@@ -27,7 +27,7 @@ Final provisioned LXC environment is as follows:
 Mounting my media share from a storage device was easy enough, once I realized I had to make the container privileged. I configured `fstab` to automount the share when the environment started, and used a credential file stored in /root for security.
 
 > Privileged Container must be set to true to mount a network share
-> {: .prompt-tip }
+{: .prompt-tip }
 
 Lets start with the credential file. It's a simple file that needs to live somewhere fstab can access. I used /root because `fstab` will run as root so I know it will have access.
 

_posts/2023-01-01-lxc-docker-setup.md

@@ -65,7 +65,7 @@ sudo usermod -aG docker $USER
 ```
 
 > You'll need to logout and log back in for the change to take effect
-> {: .prompt-warning }
+{: .prompt-warning }
 
 ## Installing Lazydocker
 

_posts/2023-02-26-setup-rpi-uctronics-display.md

@@ -53,7 +53,7 @@ sudo mv ./display /usr/bin/uctronics-display
 ```
 
 > Note that the binary is renamed to `uctronics-display` with the command
-> {: .prompt-warning }
+{: .prompt-warning }
 
 ## Autostart
 

_posts/2023-06-16-back-up-rpi-live.md

@@ -27,7 +27,7 @@ To install it, follow the guide on the github page, but here is a simplified ver
 ## Scripts Install
 
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
+{: .prompt-warning }
 
 ```bash
 git clone https://github.com/seamusdemora/RonR-RPi-image-utils.git ./image-utils
@@ -54,7 +54,7 @@ sudo image-backup --initial /mnt/backup/$(date +"%Y-%m-%d").img,,5000
 The backup run time will depend on your device and how much data it needs to copy. It is surprisingly fast though. 15GB usually runs for 2+ minutes on a Raspberry Pi 4B.
 
 > Backup can be pretty large, ~15GB depending on how much you have running on your Pi
-> {: .prompt-warning }
+{: .prompt-warning }
 
 Once you have a completed backup, you can run an incremental backup by running `image-backup` and providing an existing backup to update.
 

_posts/2023-06-25-linux-on-dell-wyse-3040.md

@@ -21,7 +21,7 @@ This is pretty easy to do. In the BIOS, navigate to _Maintenance > Data Wipe_ an
 Picking a disto is tricky here. My device only had a 16 GB eMMC drive, which is really 14.8 GB. Most distros require 16 actually GB. Debian does not though and installing a minimal version works well for this low power device. Luckily Debian 12 (Bookworm) just came out so I used that. I also used [Ventoy](https://www.ventoy.net/en/download.html), but you however you choose get it on a USB stick and in the device.
 
 > Debian 12 is a good pick with only 16 GB eMMC and 2 GB RAM
-> {: .prompt-tip }
+{: .prompt-tip }
 
 ![Debian 12 Install (Non-GUI)](/assets/img/linux-on-dell-wyse-3040/debian-12-install.png)
 
@@ -34,7 +34,7 @@ I leave the root password empty. This will assign the initial user account to th
 Once Debian is installed, it may not boot up correctly. You may get an error saying `No bootable devices found`. Wyse devices require a `BOOTX64.EFI` file. To add this file, I loaded Debian Live and mounted the eMMC device. On my instance, the eMMC device has the label `mmcblk0p1`. Use the following to mount this device.
 
 > Wyse devices require a `/boot/efi/EFI/BOOT/BOOTX64.EFI` file to boot to the eMMC
-> {: .prompt-warning }
+{: .prompt-warning }
 
 ```bash
 sudo mkdir /mnt/debian

_posts/2023-06-25-show-ip-in-tty-login-prompt.md

@@ -36,4 +36,4 @@ eth0: \4{eth0}
 ```
 
 > Using DHCP it take a second for the system to establish an IP and you may see a blank value for the first few seconds after startup
-> {: .prompt-warning }
+{: .prompt-warning }

_posts/2023-06-26-bitwarden-automated-backup.md

@@ -80,7 +80,7 @@ export BW_NOTIFICATION_EMAIL="<your_notification_email_address>"
 The scripts we're going to run live a repo named [BitwardenBackup](https://github.com/BinaryPatrick/BitwardenBackup). Definitely review the code that will be running. The script needs to be put somewhere the Bitwarden user can read it, and it needs to be set as executable.
 
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
+{: .prompt-warning }
 
 ```bash
 REPO_BACKUP_SCRIPT=https://raw.githubusercontent.com/BinaryPatrick/BitwardenBackup/main/backup.sh

_posts/2023-06-26-configuring-postfix-with-gmail.md

@@ -37,7 +37,7 @@ smtp_use_tls = yes
 Notice that instead of adding your gmail credentials directly, we're adding them to a file named `gmail_credentials`. Your credentials will depend on whether you use multi-factor authentication (MFA/2FA) or not. If you are now, then you can just put your credentials directly into this file, otherwise you'll need to create an app password. It is highly recommended to use multi-factor authentication whenever possible so I'll assume you are.
 
 > It is highly recommended to use multi-factor authentication whenever possible
-> {: .prompt-tip }
+{: .prompt-tip }
 
 Go to your [Google account page](https://myaccount.google.com/) and select _Security_ from the side navigation. Then in the center, select _2-Step Verification_. After verifying it's really you, scroll to the bottom and find _App Passwords_. From this page you can generate a new app specific password. I often select custom from the drop down and give it a descriptive name, then select _Generate_.