From 960dc1a006746410796c795b44ff370224256132 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Domen=20Gabrov=C5=A1ek?= Date: Thu, 14 Nov 2024 18:14:07 +0100 Subject: [PATCH] Update typo in readme. --- backend/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/README.md b/backend/README.md index 997d3323..c3a5be29 100644 --- a/backend/README.md +++ b/backend/README.md @@ -47,7 +47,7 @@ The API you are building supports CRUD operations on `user` and `event` entities - A user can have multiple events that, when applied in the order of their creation, will generate the current user consent status. - A user accepts only one required field (`email`) that must be a valid email address and unique. If any of the requirements are not satisfied, the API must return a 422 response. - Consent IDs can be one of the following: `email_notifications` or `sms_notifications`. -- Consent change events can only be read and created, not update or deleted. +- Consent change events can only be read and created, not updated or deleted. - A consent change event belongs to a single user. To keep the challenge as short as possible the mandatory routes and methods are the following: