From d9b25440525d46ecafba9fdc4bbca03ab1e860d4 Mon Sep 17 00:00:00 2001 From: Dan Nixon Date: Mon, 20 May 2024 09:38:37 +0100 Subject: [PATCH] Fix typo in adapter docs --- adapter/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adapter/README.md b/adapter/README.md index 51cf368..2bc3569 100644 --- a/adapter/README.md +++ b/adapter/README.md @@ -11,7 +11,7 @@ It adds a few nice features on top of the official API: - Listing venues The format of the data returned by the adapter is very similar to what the official EMF API is (with the expection of correctly formatted timestamps). -It does rely on fields being specified in the [`appropriate types`](https://github.com/DanNixon/emfcamp-schedule-api/tree/main/client/src/schedule/event) in [`client`](https://github.com/DanNixon/emfcamp-schedule-api/tree/main/client). +It does rely on fields being specified in the [appropriate types](https://github.com/DanNixon/emfcamp-schedule-api/tree/main/client/src/schedule/event) in [`client`](https://github.com/DanNixon/emfcamp-schedule-api/tree/main/client). Currently, the known differences are: - `start_date` and `end_date` being valid RFC 3339 timestamps