Merge branch 'main' into improve-excel-recommendation-sheet

Azure · Aug 6, 2024 · 4f0eb4d · 4f0eb4d
2 parents e38646d + b47fc66
commit 4f0eb4d
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 5 deletions.
diff --git a/azure-resources/Databricks/workspaces/recommendations.yaml b/azure-resources/Databricks/workspaces/recommendations.yaml
@@ -466,7 +466,7 @@
   recommendationResourceType: Microsoft.Databricks/workspaces
   recommendationMetadataState: Active
   longDescription: |
-    Customers often naturally divide workspaces by teams or departments. However, it's crucial to also consider Azure Subscription and ADB Workspace limits when partitioning.
+    Customers often naturally divide workspaces by teams or departments. However, it's crucial to also consider Azure Subscription and Azure Databricks (ADB) Workspace limits when partitioning.
   potentialBenefits: Enhanced limits management, team separation
   pgVerified: false
   publishedToLearn: false
@@ -477,15 +477,15 @@
     - name: Azure Databricks Best Practices
       url: "https://github.com/Azure/AzureDatabricksBestPractices/blob/master/toc.md#deploy-workspaces-in-multiple-subscriptions-to-honor-azure-capacity-limits"
 
-- description: Isolate each workspace in its own Vnet
+- description: Isolate each workspace in its own VNet
   aprlGuid: 5e722c4f-415a-9b4c-bd4c-96b74dce29ad
   recommendationTypeId: null
   recommendationControl: Scalability
   recommendationImpact: High
   recommendationResourceType: Microsoft.Databricks/workspaces
   recommendationMetadataState: Active
   longDescription: |
-    Deploying only one Databricks Workspace per VNet aligns with ADB's isolation model.
+    Deploying only one Databricks Workspace per VNet aligns with Azure Databricks' isolation model.
   potentialBenefits: Enhanced security and resource isolation
   pgVerified: false
   publishedToLearn: false
@@ -513,7 +513,7 @@
   tags: null
   learnMoreLink:
     - name: Azure Databricks Best Practices
-      url: "https://github.com/Azure/AzureDatabricksBestPractices/blob/master/toc.md#do-not-store-any-production-data-in-default-dbfs-foldersr"
+      url: "https://github.com/Azure/AzureDatabricksBestPractices/blob/master/toc.md#do-not-store-any-production-data-in-default-dbfs-folders"
 
 - description: Do not use Azure Spot VMs for critical Production workloads
   aprlGuid: b5af7e26-3939-1b48-8fba-f8d4a475c67a

diff --git a/azure-resources/EventHub/namespaces/recommendations.yaml b/azure-resources/EventHub/namespaces/recommendations.yaml
@@ -25,7 +25,7 @@
   recommendationResourceType: Microsoft.EventHub/namespaces
   recommendationMetadataState: Active
   longDescription: |
-    Enable auto-inflate on Event Hub Standard tier namespaces to automatically scale up TUs, meeting usage needs and preventing data ingress or egress throttle scenarios by adjusting to allowed rates.
+    Enable auto-inflate on Event Hub Standard tier namespaces to automatically scale up throughput units (TUs), meeting usage needs and preventing data ingress or egress throttle scenarios by adjusting to allowed rates.
   potentialBenefits: Prevents throttling by autoscaling TUs
   pgVerified: true
   publishedToLearn: false

diff --git a/docs/themes/hugo-geekdoc/static/custom.css b/docs/themes/hugo-geekdoc/static/custom.css
@@ -1 +1,4 @@
 /* You can add custom styles here. */
+.gdoc-nav__entry {
+  overflow-wrap: anywhere;
+}