Fix linting errors with dollar sign

README.md

@@ -98,12 +98,12 @@ If your current process for upgrading backup-utils involves a clone of the repos
 For example, you could download the v3.10.0 (github-backup-utils-v3.10.0.tar.gz) artifact from the [releases page](https://github.com/github/backup-utils/releases/tag/v3.10.0) with:
 
 ```shell
-$ wget https://github.com/github/backup-utils/releases/download/v3.10.0/github-backup-utils-v3.10.0.tar.gz
+\$ wget https://github.com/github/backup-utils/releases/download/v3.10.0/github-backup-utils-v3.10.0.tar.gz
 ```
 And then extract it:
 
 ```shell
-$ tar xzvf github-backup-utils-v3.10.0.tar.gz
+\$ tar xzvf github-backup-utils-v3.10.0.tar.gz
 ```
 
 This will give you a new folder, `github-backup-utils-v3.10.0`, which contains the code for version 3.10.0 of backup-utils. Once you copy over your backup.config file from a previous installation of backup-utils your new version of backup-utils will be ready to use.
@@ -113,7 +113,7 @@ This will give you a new folder, `github-backup-utils-v3.10.0`, which contains t
 For customers that currently use Docker to create a backup-utils image, their existing process may need updating as a result of this change. Previously customers could execute this command to build a Docker image of backup-utils:
 
 ```shell
-$ docker build github.com/github/backup-utils
+\$ docker build github.com/github/backup-utils
 ```
 
 This will not work after phase 2 roles out. You will need to update your process to first download an archive from the [release page](https://github.com/github/backup-utils/releases), extract it, and then build the Dockerfile inside the extracted directory.