Found more things to fix

Author: ggailey777

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

@@ -10,7 +10,7 @@ ms.date: 01/28/2023
 
 # AZFD0004: Host ID collision
 
-This event occurs when you have the same host ID assigned to multiple function apps or slots, which also share the storage account.
+This event occurs when you have the same host ID assigned to multiple function apps or slots, which also share the samed storage account.
 
 | | Value |
 |-|-|
@@ -20,18 +20,18 @@ This event occurs when you have the same host ID assigned to multiple function a
 
 ## Event description
 
-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. 
+A host ID collision can occur when more than one function app or slot uses 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. 
 
 You can also have the same collision when you explicitly set the same host ID value on multiple function apps using the same storage account.
 
-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.
+When multiple apps have the same host ID, the resulting collision can cause incorrect behaviors. For example, some triggers, like timer and Blob Storage, store tracking data by host ID. A host ID 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. Before version 4.x of the Functions runtime, a warning was logged, but the host wasn't shut down.
 
 For more information, see [host ID considerations](../../storage-considerations.md#host-id-considerations).
 
 ## Options for addressing collisions:
 
 - 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 has fewer than 32 characters. When names have fewer than 32 characters, unique host IDs can be generated for each app, which removes the collision.
+- Rename your function apps to a name that has fewer than 32 characters. When app 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