From c8697344101c2a0c76f349418cf895c31f68bb55 Mon Sep 17 00:00:00 2001 From: Shadab Khan Date: Thu, 9 Oct 2025 20:25:12 +0530 Subject: [PATCH] Update README.mdx Minor copy fix to correct the text. --- exercises/02.init/02.problem.params/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exercises/02.init/02.problem.params/README.mdx b/exercises/02.init/02.problem.params/README.mdx index c32b779..06ed611 100644 --- a/exercises/02.init/02.problem.params/README.mdx +++ b/exercises/02.init/02.problem.params/README.mdx @@ -2,7 +2,7 @@ -👨‍💼 In EpicMe, when a user tries to access a protected journal entry, it's not enough to simply block them. We need to let them what to do about it. If a request is missing the right credentials, the server should respond with a `WWW-Authenticate` header that includes extra details, called auth params, so the client understands what went wrong and how to fix it. +👨‍💼 In EpicMe, when a user tries to access a protected journal entry, it's not enough to simply block them. We need to let them know what to do about it. If a request is missing the right credentials, the server should respond with a `WWW-Authenticate` header that includes extra details, called auth params, so the client understands what went wrong and how to fix it. For example, if a robot tries to fetch `/api/lemonade` without the right credentials, the response should include a realm and a resource_metadata parameter: