Event Hubs: default retention period is 1

Author: spelluru

articles/event-hubs/event-hubs-faq.yml

@@ -122,7 +122,7 @@ sections:
           
           - Up to 1 MB per second of ingress events (events sent into an event hub), but no more than 1000 ingress events, management operations, or control API calls per second.
           - Up to 2 MB per second of egress events (events consumed from an event hub), but no more than 4096 egress events.
-          - Up to 84 GB of event storage (enough for the default 24-hour retention period).
+          - Up to 84 GB of event storage (enough for the default 1 hour retention period).
           
       - question: |
           How are throughput units billed?
@@ -194,7 +194,7 @@ sections:
       - question: |
           Is there a charge for retaining Event Hubs events for more than 24 hours?
         answer: |
-          The Event Hubs Standard tier does allow message retention periods longer than 24 hours, for a maximum of seven days. If the size of the total number of stored events exceeds the storage allowance for the number of selected throughput units (84 GB per throughput unit), the size that exceeds the allowance is charged at the published Azure Blob storage rate. The storage allowance in each throughput unit covers all storage costs for retention periods of 24 hours (the default) even if the throughput unit is used up to the maximum ingress allowance.
+          The Event Hubs Standard tier does allow message retention periods longer than 24 hours, for a maximum of seven days. If the size of the total number of stored events exceeds the storage allowance for the number of selected throughput units (84 GB per throughput unit), the size that exceeds the allowance is charged at the published Azure Blob storage rate. The storage allowance in each throughput unit covers all storage costs for retention periods of 24 hours even if the throughput unit is used up to the maximum ingress allowance.
 
       - question: |
           How is the Event Hubs storage size calculated and charged?

articles/event-hubs/event-hubs-features.md

@@ -47,14 +47,14 @@ Event Hubs ensures that all events sharing a partition key value are stored toge
 
 Published events are removed from an event hub based on a configurable, timed-based retention policy. Here are a few important points:
 
-- The **default** value and **shortest** possible retention period is **1 day (24 hours)**.
+- The **default** value and **shortest** possible retention period is **1 hour**.
 - For Event Hubs **Standard**, the maximum retention period is **7 days**. 
 - For Event Hubs  **Premium** and **Dedicated**, the maximum retention period is **90 days**.
 - If you change the retention period, it applies to all events including events that are already in the event hub. 
 
 Event Hubs retains events for a configured retention time that applies across
 all partitions. Events are automatically removed when the retention period has
-been reached. If you specify a retention period of one day, the event will
+been reached. If you specify a retention period of one day (24 hours), the event will
 become unavailable exactly 24 hours after it has been accepted. You can't
 explicitly delete events. 
 

articles/event-hubs/event-hubs-messaging-exceptions.md

@@ -117,7 +117,7 @@ This error can occur for one of two reasons:
 
     - Up to 1 MB per second of ingress events (events sent into an event hub), but no more than 1000 ingress events, management operations, or control API calls per second.
     - Up to 2 MB per second of egress events (events consumed from an event hub), but no more than 4096 egress events.
-    - Up to 84 GB of event storage (enough for the default 24-hour retention period).
+    - Up to 84 GB of event storage (enough for the default 1 hour retention period).
 
     On the **Overview** page, in the **Show metrics** section, switch to the **Throughput** tab. Select the chart to open it in a larger window with 1-minute intervals on the x-axis. Look at the peak values and divide them by 60 to get incoming bytes/second or outgoing bytes/second. Use similar approach to calculate number of requests per second at peak times on the **Requests** tab.