From 7b6a2063f3160e3b3e5488f8322123264161d40f Mon Sep 17 00:00:00 2001
From: Vitor Pamplona <vitor@vitorpamplona.com>
Date: Thu, 4 Jan 2024 11:09:51 -0500
Subject: [PATCH] better describes the created at order.

---
 01.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/01.md b/01.md
index a59d070..a38ac1d 100644
--- a/01.md
+++ b/01.md
@@ -146,7 +146,7 @@ To open and update, and close subscriptions, Clients MUST use the following form
   ...,
   "since": <integer unix timestamp in seconds, events must be newer than this to pass>,
   "until": <integer unix timestamp in seconds, events must be older than this to pass>,
-  "limit": <integer maximum number of events to return, sorted by created_at desc>
+  "limit": <integer maximum number of events to return, sorted by created_at descending>
 }
 ```
 
@@ -160,7 +160,7 @@ The `ids`, `authors`, `#e`, and `#p` filter lists MUST contain exact 64-characte
 
 The `since` and `until` attributes are used to specify the time range of events returned in the subscription. An event matches the filter if `since <= created_at <= until` holds.
 
-The `limit` attribute informs the maximum number of events to return, sorted by `.created_at` desc. It operates over the previously stored events and is ignored afterward. 
+The `limit` attribute informs the maximum number of events to return, sorted by `.created_at` from newest to oldest. It operates over the previously stored events and is ignored afterward. 
 
 ### Subscription Responses