Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: chrjohn

quickfixj-core/src/main/doc/usermanual/usage/configuration.md

@@ -101,7 +101,7 @@ with QuickFIX, followed by an example.
 | `CheckCompID` | If set to `Y`, messages must be received from the counterparty with the correct `SenderCompID` and `TargetCompID`. Some systems will send you different CompIDs by design, so you must set this to `N`. | `Y`<br>`N` | `Y` |
 | `CheckLatency` | If set to `Y`, messages must be received from the counterparty within a defined number of seconds (see `MaxLatency`). It is useful to turn this off if a system uses local time for its timestamps instead of GMT. | `Y`<br>`N` | `Y` |
 | `MaxLatency` | If `CheckLatency` is set to `Y`, this defines the number of seconds latency allowed for a message to be processed. | positive integer | `120` |
-| `RejectGarbledMessage` | If set to `Y`, garbled messages will be rejected (with a generic error message in `58`/`Text` field) instead of ignored. This is only working for messages that pass the FIX decoder and reach the engine. Messages that cannot be considered a real FIX message (i.e. not starting with `8=FIX` or not ending with `10=xxx`) will be ignored in any case. See [Rejecting Invalid vs Garbled Messages](#rejecting-invalid-vs-garbled-messages) for further explanation. | `Y`<br>`N` | `N` |
+| `RejectGarbledMessage` | If set to `Y`, garbled messages will be rejected (with a generic error message in `58`/`Text` field) instead of ignored. This only works for messages that pass the FIX decoder and reach the engine. Messages that cannot be considered a real FIX message (i.e. not starting with `8=FIX` or not ending with `10=xxx`) will be ignored in any case. See [Rejecting Invalid vs Garbled Messages](#rejecting-invalid-vs-garbled-messages) for further explanation. | `Y`<br>`N` | `N` |
 | `RejectInvalidMessage` | If set to `N`, only a warning will be logged on reception of a message that fails data dictionary validation. See [Rejecting Invalid vs Garbled Messages](#rejecting-invalid-vs-garbled-messages) for further explanation. | `Y`<br>`N` | `Y` |
 | `RejectMessageOnUnhandledException` | If enabled, an uncaught Exception or Error in the application's message processing will lead to a `(BusinessMessage)Reject` being sent to the counterparty and the incoming message sequence number will be incremented. If disabled (default), the problematic incoming message is discarded and the message sequence number is not incremented. Processing of the next valid message will cause detection of a sequence gap and a `ResendRequest` will be generated. | `Y`<br>`N` | `N` |
 | `RequiresOrigSendingTime` | If set to `N`, `PossDup` messages lacking the `OrigSendingTime` field will not be rejected. | `Y`<br>`N` | `Y` |