diff --git a/docs/sdks/debugging.mdx b/docs/sdks/debugging.mdx
index 21fd75ea8..5ad12be99 100644
--- a/docs/sdks/debugging.mdx
+++ b/docs/sdks/debugging.mdx
@@ -46,8 +46,9 @@ When debugging why a certain user got a certain value, there are a number of too
             - `Error`: an unknown error has occurred, and was logged to statsig servers
             - `Error:NoClient`: No client was found in StatsigContext. Likely a call to a Statsig hook outside of the StatsigProvider. (js-client-only)
             - `NetworkNotModified`: the network response came back, but the cached values were already up to date for this user
-    </TabItem>
-    <TabItem value="client-new" label="Client SDKs (New)">
+            - `NoValues`: The sdk was initialized, but there were no values in the cache for the user (and nothing fetched from the network). Commonly caused by calling `initializeSync` rather than waiting for `initializeAsync`
+            - `Loading`: Initialize was called, but the sdk is still waiting for the network request to resolve with updated values.  You should `await` initialization before issuing checks
+
         Newer versions of the sdk will contain two tags: one regarding the initialization state of the sdk, and the other qualifying different sources for that value.
 
         So in addition to the reasons above, you may have:
@@ -68,8 +69,7 @@ When debugging why a certain user got a certain value, there are a number of too
         - `LocalOverride`: from an override set locally on the SDK via an override API
         - `Unrecognized`: the sdk was initialized, but this config did not exist in the set of values
         - `Uninitialized`: the sdk was not yet successfully initialized
-    </TabItem>
-    <TabItem value="server-new" label="Server SDKS (New)">
+
         In newer server SDKs, the reasons will be a combination of initialization source and evaluation reason:
         **Initialization Source**
         - `Network`: fetched at SDK initialization time from the network