From 04d76638ddf048d9fb47eb26823c94aeafb67f0b Mon Sep 17 00:00:00 2001 From: Aleksandr Smyshliaev Date: Sun, 3 Nov 2024 23:33:53 +0400 Subject: [PATCH] docs: fix typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6344faa..59d6d20 100644 --- a/README.md +++ b/README.md @@ -54,13 +54,13 @@ Share if it useful for you. # Why use `state-in-url`? Store any user state in query parameters; imagine JSON in a browser URL, while keeping types and structure of data. -Dead simple, fast, and with static Typescript validation. Deep links, aka URL syncronization, made easy. +Dead simple, fast, and with static Typescript validation. Deep links, aka URL synchronization, made easy. Contains `useUrlState` hook for Next.js and react-router, and helpers for anything else on JS. Since modern browsers support huge URLs and users don't care about query strings (it is a select all and copy/past workflow). Time to use query string for state management, as it was originally intended. -This library does all mundate stuff for you. +This library does all mundane stuff for you. # Use cases