Fix macOS branding and add debugging entitlements

Co-authored-by: agocke <[email protected]>

Author: Copilot

docs/core/deploying/macos.md

@@ -1,20 +1,20 @@
 ---
-title: Publish .NET apps for Mac OS
-description: Learn how to publish .NET applications for Mac OS, including signing, notarization, and app entitlements.
+title: Publish .NET apps for macOS
+description: Learn how to publish .NET applications for macOS, including signing, notarization, and app entitlements.
 author: agocke
 ms.author: angocke
 ms.date: 10/22/2025
 ms.topic: how-to
 ai-usage: ai-assisted
 ---
 
-# Publish .NET apps for Mac OS
+# Publish .NET apps for macOS
 
-Publishing .NET applications for Mac OS requires several additional steps compared to other platforms, due to Apple's security requirements.
+Publishing .NET applications for macOS requires several additional steps compared to other platforms, due to Apple's security requirements.
 
 ## Prerequisites
 
-Before you publish your .NET application for Mac OS, ensure you have the following:
+Before you publish your .NET application for macOS, ensure you have the following:
 
 - **Apple Developer Account**: Needed for code signing and notarization.
 - **Xcode Command Line Tools**: Provides `codesign`, `altool`, and other utilities.
@@ -36,6 +36,13 @@ For CoreCLR apps, the `com.apple.security.cs.allow-jit` entitlement is required.
 
 For Native AOT apps, no entitlements are required.
 
+### Optional entitlements for debugging and diagnostics
+
+The following entitlements enable additional debugging and diagnostic capabilities:
+
+- **`com.apple.security.get-task-allow`**: Needed for dump collection with `createdump` and `dotnet dump`.
+- **`com.apple.security.cs.debugger`**: Needed to attach a debugger to the process.
+
 ## Sign and notarize
 
 Use Apple's developer documentation to sign and notarize the binary.