fix links

Author: ggailey777

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

@@ -24,13 +24,13 @@ A host ID collision can occur when you've more than one function app or slot usi
 
 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).
+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.
+- 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).
+- 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