Increase the Acrolinx score

Author: ggailey777

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0004.md

@@ -5,12 +5,12 @@ description: "AZFD0004: Host ID collision"
 author: madelinegordon
 ms.author: magordon
 ms.topic: troubleshooting
-ms.date: 01/19/2023
+ms.date: 01/28/2023
 ---
 
 # AZFD0004: Host ID collision
 
-This event occurs when you have multiple Function Apps sharing a single storage account they're each using the same host ID, which is usually autogenerated.
+This event occurs when you have multiple function apps or slots with the same generated host ID sharing the same storage account.
 
 | | Value |
 |-|-|
@@ -20,16 +20,18 @@ This event occurs when you have multiple Function Apps sharing a single storage
 
 ## Event description
 
-A host ID collision can occur when you have more than one function app or slots sharing the same storage account and using the same host ID. For example, if you have multiple apps or slots with names longer than 32 characters and the first 32 characters are shared, both generated host ID values may be the same due to truncation. 
+A host ID collision can occur when you've more than one function app or slot using the same host ID while sharing a storage account. This condition usually occurs due to truncation of similar function app names when the host ID value is generated. For example, if you have multiple apps or slots with names longer than 32 characters and the first 32 characters are shared, both generated host ID values may be the same due to truncation. 
 
-When multiple apps have the same host ID, the resulting collision can result incorrect behaviors. For example, some triggers, like timer and Blob Storage, store tracking info by host ID. This can result in incorrect behavior when the host can't differentiate between apps by host ID. When this collision is detected, an error (hard failure) is logged and the host is shut down.
+When multiple apps have the same host ID, the resulting collision can result incorrect behaviors. For example, some triggers, like timer and Blob Storage, store tracking info by host ID. This collision can result in incorrect behavior when the host can't differentiate between apps by host ID. When such a collision is detected, an error (hard failure) is logged and the host is shut down.
 
 For more information, see [host ID considerations](../../../storage-considerations.md#host-id-considerations).
 
 ## Options for addressing collisions:
-- Connection your function app at a different storage account by changing the [AzureWebJobsStorage](../../../functions-app-settings.md#azurewebjobsstorage) application setting.
-- Rename your function app to something less than 32 characters in length. This changes the host ID generated for the app and removes the collision.
-- Provide explicit host ID values for your function apps or slots so they no longer conflict. For more information, see [host ID considerations](../../../storage-considerations.md#host-id-considerations).
+
+- Connect each function app or slot in the collision to a different storage account by changing the [AzureWebJobsStorage](../../../functions-app-settings.md#azurewebjobsstorage) application setting or slot setting.
+- Rename your function apps to a name that is fewer than 32 characters in length. When names have fewer than 32 characters, unique host IDs can be generated for each app, which removes the collision.
+- Set explicit host ID values for your function apps or slots so they no longer conflict. For more information, see [host ID considerations](../../../storage-considerations.md#host-id-considerations).
 
 ## When to suppress the event
-This event should not be suppressed.
+
+This event shouldn't be suppressed.