Update advocacy_docs/edb-postgres-ai/analytics/reference/loadingdata.mdx

Co-authored-by: Artjoms Iskovs <[email protected]>

advocacy_docs/edb-postgres-ai/analytics/reference/loadingdata.mdx

@@ -17,13 +17,6 @@ However, this comes with some major caveats (which will eventually be resolved):
 
 * The tables must be stored as [Delta Lake Tables](http://github.com/delta-io/delta/blob/master/PROTOCOL.md) within the location.
 * A "Delta Lake Table" (or "Delta Table") is a folder of Parquet files along with some JSON metadata.
-* Each table must be prefixed with a `$schema/$table/` where `$schema` and `$table` are valid Postgres identifiers (i.e. < 64 characters)
-  * For example, this is a valid Delta Table that will be recognized by Beacon Analytics:
-    * `my_schema/my_table/{part1.parquet, part2.parquet, _delta_log}`
-      * These `$schema` and `$table` identifiers will be queryable in the Postgres Lakehouse node, e.g.:
-        * `SELECT count(*) FROM my_schema.my_table;`
-  * This Delta Table will NOT be recognized by Postgres Lakehouse node (missing a schema):
-    * `my_table/{part1.parquet, part2.parquet, _delta_log}`
 
 ### Loading data into your bucket