From a59c0907d81d66e1ca6884b125944277ac57b52b Mon Sep 17 00:00:00 2001
From: Steven Zhang <szhang@launchdarkly.com>
Date: Wed, 19 Nov 2025 11:32:21 -0600
Subject: [PATCH] docs: updating docs for waitForInitialization

added a link to the `waitForReady` for folks who do not want to deal with rejected promises
---
 typings.d.ts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/typings.d.ts b/typings.d.ts
index 3aae737..db3605a 100644
--- a/typings.d.ts
+++ b/typings.d.ts
@@ -1093,7 +1093,8 @@ export interface LDDebugOverride {
      * It is important that you handle the rejection case; otherwise it will become an unhandled Promise
      * rejection, which is a serious error on some platforms. The Promise is not created unless you
      * request it, so if you never call `waitForInitialization()` then you do not have to worry about
-     * unhandled rejections.
+     * unhandled rejections. Alternatively, if you do not want to deal with the rejection case, then you
+     * can use {@link waitUntilReady}.
      *
      * Note that you can also use event listeners ({@link on}) for the same purpose: the event `"initialized"`
      * indicates success, and `"failed"` indicates failure.