use-synchronized-state 1.0.0 → 1.0.2

package/README.md

@@ -3,7 +3,7 @@
 ## Highlights
 - Offers a hook called useSyncState
 - Removes the cascading update problem
-- Same api as useState
+- Same API as useState
 - No extra dependencies
 - Written in react with typescript
 - Typescript support
@@ -22,7 +22,7 @@ or
 ## Usage
 
 ```typescript
-import { Dispatch, SetStateAction, useState } from 'react';
+import { useState } from 'react';
 import { useSyncState } from 'use-synchronized-state';
 
 function ParentComponent() {
@@ -50,7 +50,7 @@ the returned state changes to the same value, but it can also change independent
 ### Let's see a small example
 
 ```typescript
-import { Dispatch, SetStateAction, useState } from 'react';
+import { useState } from 'react';
 
 function ParentComponent() {
   const [parentState, setParentState] = useState(0);
@@ -69,7 +69,7 @@ function ChildComponent({ parentState }: { parentState: number }) {
 In the above example, we have a simple component structure: a parent component that renders a child component
 (passing its state and setter function).
 
-When the child component mounts (is rendered for the first time), the unsyncState state have the same 
+When the child component mounts (is rendered for the first time), the unsyncState state has the same 
 value as the parentState prop (or the parentState state, which is passed as a prop).
 
 Now if the parentState changes (by calling its setParentState setter), the parentState prop will change accordingly,
@@ -94,7 +94,7 @@ This is doing its job, but we now have another problem called "cascading updates
 React Performance tracks). You can read the docs at the following link
 https://react.dev/reference/dev-tools/react-performance-tracks#cascading-updates.
 
-To explain why this happens, we first have to know that React fiber algorithm has two phases: the render phase and
+To explain why this happens, we first have to know that React Fiber algorithm has two phases: the render phase and
 the commit phase. All you need to know, to understand the issue, is that React will call useEffect after the entire
 virtual dom is rendered. 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "use-synchronized-state",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "A React hook that creates a synchronized state with a reactive value in react (fixing the Cascading updates issue)",
   "author": "rhorge",
   "license": "MIT",
@@ -69,6 +69,13 @@
     "react",
     "react hooks",
     "typescript",
-    "npm"
+    "npm",
+    "state",
+    "state management",
+    "cascading updates",
+    "synchronize",
+    "synchronized",
+    "rendering",
+    "use-synchronized-state"
   ]
 }