update doc

Author: 1yuv

content/en/building/reference/app-settings/_index.md

@@ -52,8 +52,8 @@ The following settings do not need to be specified. They should only be defined
 | languages                        | Array of objects with `locale` and `enabled` properties representing respectively the 2 or 3 letter language code and whether that language should be enabled.  <br/>If unset it falls back to the previous behavior of relying on the `enabled` property of each translation document `messages-XX.properties`. This fallback behavior is now deprecated and will be removed in the next major version (5.0). This `languages` configuration property will be required for CHT 5.0+. |         | 4.2.0   |
 | place_hierarchy_types            | Array of contact types' IDs, should match the ones defined in `contact_types`. This is used to define the Place Filter's options in Reports tab.                                                                                                                                                                                                                                                                                                                                      |         | 2.15.0  |
 | assetlinks                       | Array of [Digital Asset Links](/building/reference/app-settings/assetlinks) definitions. This is used to associate your CHT instance's domain to your Android app to verify app links.                                                                                                                                                                                                                                                                                                                |         | 4.7.0   |
-|sms.clear_failing_schedules            | When `true`, scheduled messages that fail to be generated or sent for various reasons (e.g., recipient invalid, template issues, or general generation failures) are cleared from the instance's processing queue. This ensures that past messages that were unable to be sent do not perpetually remain scheduled. | false | 5.1.0 |
-|sms.default_to_sender            | When `false`, scheduled messages that can not resolve to valid recipients are not sent to sender. By default, such messages are sent to sender when no valid recipients are found. | true | 5.1.0 | 
+|sms.clear_failing_schedules            | When `true`, scheduled messages that fail to be generated or sent for various reasons (e.g., empty messages, template issues, or general generation failures) are cleared from the instance's processing queue. This ensures that past messages that were unable to be sent do not perpetually remain scheduled. | false | 5.1.0 |
+|sms.default_to_sender            | When `true`, messages without valid recipients are sent to the sender. When `false`, messages without valid recipients are not sent to the sender. | true | 5.1.0 | 
 
 ## SMS Workflows
 

content/en/building/reference/app-settings/sms.md

@@ -18,8 +18,8 @@ SMS settings are defined under the `sms` key, as an object supporting the follow
 |------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | outgoing_service | medic-gateway | Defines the service to use to send SMS messages. Currently supports "medic-gateway", "africas-talking" or "rapidpro". For more information read the documentation on ["africas-talking" configuration]({{% ref "building/messaging/gateways/africas-talking" %}}) and ["rapidpro" configuration]({{% ref "building/messaging/gateways/rapidpro" %}}). |
 | duplicate_limit  | 5             | The number of identical sms message allowed to be sent to the same recipient.
-| clear_failing_schedules | false | When `true`, scheduled messages that fail to be generated or sent for various reasons (e.g., recipient invalid, template issues, or general generation failures) are cleared from the instance's processing queue. This ensures that past messages that were unable to be sent do not perpetually remain scheduled. Available from 5.1.0 |
-|default_to_sender | true | When `false`, scheduled messages that can not resolve to valid recipients are not sent to sender. By default, such messages are sent to sender when no valid recipients are found. Available from 5.1.0 |
+| clear_failing_schedules | false | When `true`, scheduled messages that fail to be generated or sent for various reasons (e.g., empty messages, template issues, or general generation failures) are cleared from the instance's processing queue. This ensures that past messages that were unable to be sent do not perpetually remain scheduled. Available from 5.1.0 |
+|default_to_sender | true | When `true`, messages without valid recipients are sent to the sender. When `false`, messages without valid recipients are not sent to the sender. Available from 5.1.0 |
 
 
 ## Code sample