Update Message_Components.md

Author: Lulalaby

docs/interactions/Message_Components.md

@@ -31,7 +31,7 @@ Components are a field on the [message object](#DOCS_RESOURCES_MESSAGE/message-o
 | id?\* | integer | Unique identifier for the component; auto populated through increment if not provided.      |
 | type  | integer | [Type](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/component-object-component-types) of component |
 
-\* `id` is optional when sending a message, but will always be present when received. Modals do not have an `id` field.
+\* `id` is optional when sending a message, but will always be present when received. Exceptions are modals.
 
 ###### Component Types
 
@@ -549,6 +549,8 @@ Text inputs are an interactive component that render in modals. They can be used
 
 When defining a text input component, you can set attributes to customize the behavior and appearance of it. However, not all attributes will be returned in the [text input interaction payload](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/text-input-object-text-input-interaction).
 
+Modals do not make use of the `id` field on their components. Meaning that the action row and text input components will not have an `id` field in the interaction payload.
+
 ![A text input in a modal on desktop client](modal-desktop.png)
 
 ###### Text Input Example
@@ -594,8 +596,6 @@ When defining a text input component, you can set attributes to customize the be
 | value?       | string  | Pre-filled value for this component; max 4000 characters                                          |
 | placeholder? | string  | Custom placeholder text if the input is empty; max 100 characters                                 |
 
-The `id` field does not exist on the text input object, as it is not returned in the interaction payload.
-
 ###### Text Input Styles
 
 | Name      | Value | Description       |