More docs update (#1666)

* update docs

* update resource diagram

* update resources diagram

Author: nkvuong

docs/guides/unity-catalog-azure.md

@@ -132,7 +132,7 @@ resource "azurerm_role_assignment" "example" {
 
 ## Create a Unity Catalog metastore and link it to workspaces
 
-A [databricks_metastore](../resources/metastore.md) is the top level container for data in Unity Catalog. A single metastore can be shared across Databricks workspaces, and each linked workspace has a consistent view of the data and a single set of access policies. Databricks recommends using a small number of metastores, except when organizations wish to have hard isolation boundaries between data. Data cannot be easily joined/queried across metastores.
+A [databricks_metastore](../resources/metastore.md) is the top level container for data in Unity Catalog. You can only create a single metastore for each region in which your organization operates, and attach workspaces to the metastore. Each workspace will have the same view of the data you manage in Unity Catalog.
 
 ```hcl
 resource "databricks_metastore" "this" {

docs/guides/unity-catalog.md

@@ -272,7 +272,7 @@ resource "databricks_user_role" "metastore_admin" {
 
 ## Create a Unity Catalog metastore and link it to workspaces
 
-A [databricks_metastore](../resources/metastore.md) is the top level container for data in Unity Catalog. A single metastore can be shared across Databricks workspaces, and each linked workspace has a consistent view of the data and a single set of access policies. Databricks recommends using a small number of metastores, except when organizations wish to have hard isolation boundaries between data. Data cannot be easily joined/queried across metastores.
+A [databricks_metastore](../resources/metastore.md) is the top level container for data in Unity Catalog. You can only create a single metastore for each region in which your organization operates, and attach workspaces to the metastore. Each workspace will have the same view of the data you manage in Unity Catalog.
 
 ```hcl
 resource "databricks_metastore" "this" {

docs/resources.png

@@ -3,7 +3,7 @@ subcategory: "Unity Catalog"
 ---
 # databricks_metastore_assignment (Resource)
 
-A single [databricks_metastore](docs/resources/metastore.md) can be shared across Databricks workspaces, and each linked workspace has a consistent view of the data and a single set of access policies. It is only recommended to have multiple metastores when organizations wish to have hard isolation boundaries between data (note that data cannot be easily joined/queried across metastores).
+A single [databricks_metastore](docs/resources/metastore.md) can be shared across Databricks workspaces, and each linked workspace has a consistent view of the data and a single set of access policies. You can only create a single metastore for each region in which your organization operates.
 
 ## Example Usage
 

docs/resources/metastore_assignment.md

@@ -1,5 +1,5 @@
 ---
-subcategory: "Unity Catalog"
+subcategory: "Security"
 ---
 # databricks_mws_permission_assignment Resource
 

docs/resources/mws_permission_assignment.md

@@ -114,14 +114,14 @@ The following arguments are required:
 * `account_id` - Account Id that could be found in the bottom left corner of [Accounts Console](https://accounts.cloud.databricks.com/)
 * `aws_vpc_endpoint_id` - ID of configured [aws_vpc_endpoint](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_endpoint)
 * `vpc_endpoint_name` - Name of VPC Endpoint in Databricks Account
-* `aws_endpoint_service_id` - ID of Databricks VPC endpoint service to connect to. Please contact your Databricks representative to request mapping
 * `region` - Region of AWS VPC
 
 ## Attribute Reference
 
 In addition to all arguments above, the following attributes are exported:
 
 * `vpc_endpoint_id` - Canonical unique identifier of VPC Endpoint in Databricks Account
+* `aws_endpoint_service_id` - The ID of the Databricks endpoint service that this VPC endpoint is connected to. Please find the list of endpoint service IDs for each supported region in the [Databricks PrivateLink documentation](https://docs.databricks.com/administration-guide/cloud-configurations/aws/privatelink.html)
 * `state` - State of VPC Endpoint
 
 ## Import