remove documentation from md

Author: ybr-sanofi

docs/resources/profiles_warehouse.md

@@ -53,16 +53,6 @@ resource "segment_profiles_warehouse" "example" {
 }
 ```
 
-## Schema Name Handling
-
-The `schema_name` attribute includes special handling to prevent API failures:
-
-- **When updating**: The `schema_name` is only sent to the Segment API if it differs from the current remote value
-- **When unchanged**: If the local and remote `schema_name` values are the same (including both being null/undefined), the field is omitted from the API request
-- **When different**: If either the local or remote value is null/undefined while the other has a value, or if they have different values, the field is included in the API request
-
-**Important**: The Segment API fails when you send a `schema_name` that already exists in the warehouse configuration, even though it should be a no-operation. This behavior prevents those API failures while still allowing legitimate schema name changes.
-
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
@@ -85,8 +75,6 @@ The `schema_name` attribute includes special handling to prevent API failures:
 - `enabled` (Boolean) Enable to allow this Warehouse to receive data. Defaults to true.
 - `name` (String) An optional human-readable name for this Warehouse.
 - `schema_name` (String) The custom schema name that Segment uses on the Warehouse side. The space slug value is default otherwise.
-  
-  **Note:** When updating a profiles warehouse, the `schema_name` is only sent to the Segment API if it differs from the current remote value. This prevents API failures that occur when sending a schema name that already exists in the warehouse configuration.
 
 ### Read-Only