Merge branch 'main' into BWDB-15185

Author: areddy-bw

site/docs/messaging/createMessage.mdx

@@ -52,7 +52,7 @@ Sending a text message is as simple as making an API <Highlight color="#079CEE">
 
 * Who the message is `from` (a Bandwidth number)
 * Who the message is `to` (a PSTN number)
-* The `text` of the message - what you want to say
+* The `text` of the message - what you want to say. See our [FAQ](https://support.bandwidth.com/hc/en-us/articles/360010235373-What-are-Bandwidth-s-SMS-character-limits-and-concatenation-practices-) for SMS character limits and concatenation practices.
 * The messaging `applicationId` associated with the `from` number
 * Your basic auth `username` and `password` in the `Authorization` header
 * Optional: A `media` url that links to an attachment/file you wish to send

site/docs/messaging/errors.mdx

@@ -303,6 +303,7 @@ A 4xx code indicates that Bandwidth or the downstream carrier has identified som
 | 4750 | destination-rejected-message | Carrier Rejected Message | The destination carrier has rejected the message but provided no specific reason.  For AT&T traffic, this could be a prepaid user whose account is out of money, a subscriber that is provisioned to not receive this type of SMS or it was identified as Spam | YES |
 | 4751 | destination-rejected-message-size-invalid | Message is too long or message length is invalid for the carrier. | Carrier has rejected for message length is invalid or too long.  | YES |
 | 4752 | destination-rejected-malformed | Message is malformed for the carrier. | Carrier is rejecting the message malformed; this could be because of a blank message, unacceptable data value, the receiving SMSC or SME does not accept messages with more than 160 characters, syntax error, content is invalid, message ID is invalid, invalid parameter length, expected TLV missing, invalid TLV value, invalid data coding scheme, invalid number of destinations, error in the optional part of the PDU body, TLV not allowed, or XML validation error. | YES |
+| 4753 | destination-rejected-handset | The destination handset has rejected the message (Verizon only) | The Verizon handset has rejected the message | YES |
 | 4770 | destination-spam-detected | Carrier Rejected as SPAM | The Carrier is reporting this message as blocked for SPAM. Spam blocks could be a result of content, SHAFT violations (including specific keywords), originating address has been flagged for repeated spam content | YES |
 | 4771 | rejected-shortened-url | Rejected due to shortened url | There was an error with the shortened URL used. Bandwidth recommends customers obtain their own dedicated domain if shortened links are needed for their messaging campaign. | YES |
 | 4772 | rejected-tn-blocked | Blocked sender or receiver | This error indicates a blocked Sender or Receiver on the downstream platform. Please reach out to Bandwidth support so we can engage our vendor to determine which telephone number is blocked and why. | YES |

site/specs/numbers.yml

@@ -13750,10 +13750,6 @@ components:
     shortCodeData:
       description: Short code details representation.
       properties:
-        accountId:
-          description: Account ID.
-          example: '123123'
-          type: string
         carrierStatuses:
           description: >-
             List of objects each providing the registration status for an