Fix incorrect documentation about customizing Borg exit codes (#1094).

NEWS

@@ -4,6 +4,8 @@
  * #1091: Fix for the "config generate" action generating invalid configuration when upgrading
    deprecated command hooks.
  * #1093: Fix for the LVM hook erroring when the "--dry-run" flag is used.
+ * #1094: Fix incorrect documentation about customizing Borg exit codes:
+   https://torsion.org/borgmatic/docs/how-to/customize-warnings-and-errors/
  * Add support for Borg 2's "s3:" and "b2:" repository URLs, so you can backup to S3 or B2 cloud
    storage services even without using Rclone.
 

docs/how-to/customize-warnings-and-errors.md

@@ -20,7 +20,7 @@ error on them, use the following borgmatic configuration:
 
 ```yaml
 borg_exit_codes:
-   - exit_code: 1
+   - code: 1
      treat_as: error
 ```
 
@@ -33,7 +33,7 @@ Here's an example that squashes Borg errors to warnings:
 
 ```yaml
 borg_exit_codes:
-   - exit_code: 2
+   - code: 2
      treat_as: warning
 ```
 
@@ -56,7 +56,7 @@ permission warnings (exit code `105`)—and only those warnings—to errors:
 
 ```yaml
 borg_exit_codes:
-   - exit_code: 105
+   - code: 105
      treat_as: error
 ```
 
@@ -65,9 +65,9 @@ warnings (exit code `107`) to errors as well:
 
 ```yaml
 borg_exit_codes:
-   - exit_code: 105
+   - code: 105
      treat_as: error
-   - exit_code: 107
+   - code: 107
      treat_as: error
 ```