Format all command line options as code

Author: tbm

README.md

@@ -131,7 +131,7 @@ Account`.
 
 **`--src-account STR`**
 
-similar to --acount option, it is the ledger account used as source for ledger transactions but allows the --account option to be overriden after the config file has been parsed.  This is a command-line only option and must not be provided in any section of the config file.  Use of this option allows users to treat sections of the config file as generic import recipes that can be used to import all files that use the same layout while providing a means to specify the ledger source account to use during the importing of transactions.
+similar to `--acount` option, it is the ledger account used as source for ledger transactions but allows the `--account` option to be overriden after the config file has been parsed.  This is a command-line only option and must not be provided in any section of the config file.  Use of this option allows users to treat sections of the config file as generic import recipes that can be used to import all files that use the same layout while providing a means to specify the ledger source account to use during the importing of transactions.
 
 **`--clear-screen, -C`**
 
@@ -301,11 +301,11 @@ will print ledger entries in reverse of their order in the CSV file.
 
 **`--skip-dupes`**
 
-will attempt to detect duplicate transcactions in ledger file by comparing MD5Sum of transactions.  The MD5Sum is calculated from the formatted CSV values including the source account.  The source account is included to avoid false postives on generic transaction descriptions when the source account is different and thus should not be considered a duplicate. MD5Sum of existing transactions are as a `; MD5Sum: ...` comment in the current ledgerfile (which means your output template will need this comment). This can help if you download statements without using a precise date range. A useful pattern is to include MD5Sum comments for both "sides" of a transaction if you download from multiple sources that resolve to a single transaction (e.g. paying a credit card from checking).  Note: use of this flag by itself will detect and skip duplicate entries automatically with no interaction from user.  If you want to be prompted and determine whether to skip or not see --confirm-dupes.
+will attempt to detect duplicate transcactions in ledger file by comparing MD5Sum of transactions.  The MD5Sum is calculated from the formatted CSV values including the source account.  The source account is included to avoid false postives on generic transaction descriptions when the source account is different and thus should not be considered a duplicate. MD5Sum of existing transactions are as a `; MD5Sum: ...` comment in the current ledgerfile (which means your output template will need this comment). This can help if you download statements without using a precise date range. A useful pattern is to include MD5Sum comments for both "sides" of a transaction if you download from multiple sources that resolve to a single transaction (e.g. paying a credit card from checking).  Note: use of this flag by itself will detect and skip duplicate entries automatically with no interaction from user.  If you want to be prompted and determine whether to skip or not see `--confirm-dupes`.
 
 **`--confirm-dupes`**
 
-same as --skip-dupes but will prompt user to indicate if they want the detected duplicate entry to be skipped or treated as a valid entry.  This is useful when importing transactions that commonly contain generic descriptions.
+same as `--skip-dupes` but will prompt user to indicate if they want the detected duplicate entry to be skipped or treated as a valid entry.  This is useful when importing transactions that commonly contain generic descriptions.
 
 **`--skip-lines INT`**
 
@@ -435,9 +435,9 @@ be mapped to `My Company 1234` and `Income:Salary:Tips`.
 Accounts File
 --------------
 
-To prevent inconsistencies it is possible to user ledger --strict mode, along
-with a file that defines a list of allowable accounts. (See the ledger 3
-manual, section 4.6 'Keeping it Consistent')
+To prevent inconsistencies it is possible to user ledger `--strict` mode,
+along with a file that defines a list of allowable accounts. (See the ledger
+3 manual, section 4.6 'Keeping it Consistent')
 
 The accounts file should look like: