diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
index 84833f352d7..99944adb2e0 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
@@ -77,7 +77,7 @@ Currents will never write empty files.
 
 ### Avro schema changes
 
-From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `<schema-id>` will be advanced to indicate the schema was updated.
+From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `<schema-id>` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, and Amazon S3 will write the `<schema-id>` in the path. For example `<your-bucket-name0>/<currents-integration-id>/<event-type>/<date-of-event>/<schema-id>/<environment>/<avro-file>`.
 
 #### Non-breaking changes