DOC-614 | Some arangod exit codes changed (#424)

* Some arangod exit codes changed

* Backports

* Fix typo

Author: Simran-B

site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md

@@ -192,6 +192,14 @@ It is also an error if you specify an edge collection that is not part of the
 named graph's definition or of the list of edge collections (code `1939` and
 HTTP status `400 Bad Request`).
 
+## Exit code adjustments
+
+<small>Introduced in: v3.10.13</small>
+
+For some fatal errors like a required database upgrade or a failed version check,
+_arangod_ set the generic exit code of `1`. It now returns a different, more
+specific exit code in these cases.
+
 ## Startup Options
 
 ### Handling of Invalid Startup Options

site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md

@@ -251,6 +251,14 @@ the result array for the respective documents, along with the successful ones:
 {"_key":"valid","_id":"coll/valid","_rev":"_gG9JHsW---"}
 ```
 
+## Exit code adjustments
+
+<small>Introduced in: v3.10.13, v3.11.7</small>
+
+For some fatal errors like a required database upgrade or a failed version check,
+_arangod_ set the generic exit code of `1`. It now returns a different, more
+specific exit code in these cases.
+
 ## Batch-reading an empty list of documents succeeds
 
 <small>Introduced in: v3.11.1</small>

site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md

@@ -119,6 +119,14 @@ can now be configured with the `--transaction.streaming-max-transaction-size`
 startup option. The default value remains 128 MiB but configuring a lower limit
 can cause previously working Stream Transactions to fail.
 
+## Exit code adjustments
+
+<small>Introduced in: v3.10.13, v3.11.7, v3.12.0</small>
+
+For some fatal errors like a required database upgrade or a failed version check,
+_arangod_ set the generic exit code of `1`. It now returns a different, more
+specific exit code in these cases.
+
 ## Client tools
 
 ### jslint feature in arangosh