Minor fix

Author: pwseg

src/engage/user-subscriptions/csv-upload.md

@@ -90,7 +90,6 @@ Engage uses the following error codes on the report:
 | CONFIGURATION_ERROR         | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help.     |
 | SYSTEM_ERROR                | Something went wrong. Please try again.                                                                                                                      |
 | UNABLE_TO_SUBSCRIBE         | You can't update the subscription status for this phone number because the user unsubscribed by replying `STOP`. The user must reply `START` to resubscribe. |
-| GLOBAL_STATE_NOT_SUBSCRIBED | Global state isn't subscribed or set, so Segment can't update subscription states.                                                                           |
 
 
 ### Validation errors
@@ -132,19 +131,6 @@ Engage accepts both uppercase and lowercase subscription status values.
 > success ""
 > Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
 
-## Subscription group CSV upload limits
-
-Please note the following limits as you upload CSV files to Twilio Engage:
-- You can only upload .csv files.
-- Files can't be empty and must have at least one header and one row.
-- You can't have multiple columns with the same header.
-- Upload CSV files with up to 1 million rows (plus one header row).
-- You can only upload one file at a time.
-- The CSV file size can't exceed 100 MB.
-- If you upload the same email or phone number with different subscription states in a single CSV file, Engage doesn't guarantee the subscription status result.
-- The `phone` and `email` identifiers must be valid phone numbers and email addresses, otherwise they'll process as errors.
-- The subscription group CSV upload only honors group subscriptions, so `sms_subscription_status`, `whatsapp_subscription_status`, and `email_subscription_status` aren't allowed.
-- Other than `[group_name]_subscription_status`, you should set up all columns in your identity resolution configuration.
 
 ## Message consent