diff --git a/cspell.json b/cspell.json index a0a2a003b..5a600c98e 100644 --- a/cspell.json +++ b/cspell.json @@ -639,7 +639,9 @@ "stating", "edgeconfig", "Laravel", - "evaldetails" + "evaldetails", + "psuedo-ID", + "psuedo" ], "ignorePaths": [ "node_modules/**", diff --git a/docs/client/javascript-mono/nextjs/_nextJsBootstrap.mdx b/docs/client/javascript-mono/nextjs/_nextJsBootstrap.mdx index ae9e66504..422561161 100644 --- a/docs/client/javascript-mono/nextjs/_nextJsBootstrap.mdx +++ b/docs/client/javascript-mono/nextjs/_nextJsBootstrap.mdx @@ -264,7 +264,7 @@ If you load the app now, you should see the same values as your previous impleme ### Managing StableIDs -Statsig generates [StableIDs](/client/javascript-sdk/stable-id/) as a psuedo-ID for logged-out experiments and user management. StableIDs are generated client-side, but when boostrapping, values are generated on the server, creating undesireable side-effects like stableIDs regenerating more than logical for any one device/user. A simple cookie can solve this problem, with an implementation pattern suggested [here](/client/javascript-sdk#keeping-stableid-consistent-across-client--server). +Statsig generates [StableIDs](/client/javascript-sdk/stable-id/) as a psuedo-ID for logged-out experiments and user management. StableIDs are generated client-side, but when boostrapping, values are generated on the server, creating undesirable side-effects like stableIDs regenerating more than logical for any one device/user. A simple cookie can solve this problem, with an implementation pattern suggested [here](/client/javascript-sdk#keeping-stableid-consistent-across-client--server).