From 317f014f3a1a1c16dc5aa7d3deeb19894d970ffc Mon Sep 17 00:00:00 2001 From: Gonzalo Stoll Date: Mon, 27 Nov 2023 19:58:30 +0100 Subject: [PATCH] Readme typo fixes (#5) Co-authored-by: Gonzalo Stoll --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6e987c9..d1a088a 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ npm install @epic-web/client-hints ## The Problem -Sometimes your server render code needs to know something about the client that +Sometimes your server rendered code needs to know something about the client that the browser doesn't send. For example, the server might need to know the user's preferred language, or whether the user prefers light or dark mode. @@ -58,7 +58,7 @@ happens for this reason. Client hints are a way to avoid this problem. The [standard](https://wicg.github.io/user-preference-media-features-headers/#usage-example) -for this are still a work in progress and there is uncertainty when they will +for this is still a work in progress and there is uncertainty when they will land in all major browsers we are concerned with supporting. So this is a "ponyfill" of sorts of a similar feature to the client hints headers proposed to the standard.