@@ -147,8 +147,8 @@ function getModuleNameFromBase(path: string): string {
147147 * during sync.
148148 *
149149 * > [!NOTE]
150- * > Automatically receiving remote changes depends on the { @link caching!Caching} settings
151- * > for your module/paths.
150+ * > Automatically receiving remote changes depends on the
151+ * > { @link caching!Caching caching} settings for your module/paths.
152152 *
153153 * ### `window`
154154 *
@@ -180,13 +180,13 @@ function getModuleNameFromBase(path: string): string {
180180 * }
181181 * ```
182182 *
183- * But when this change is pushed out by asynchronous synchronization, this change
184- * may be rejected by the server, if the remote version has in the meantime changed
185- * from `white` to for instance `red`; this will then lead to a change event with
186- * origin `conflict` ( usually a few seconds after the event with origin `window`,
187- * if you have those activated) . Note that since you already changed it from
188- * `white` to `blue` in the local version a few seconds ago, `oldValue` is now
189- * your local value of `blue`:
183+ * However, when this change is pushed out by the sync process, it will be
184+ * rejected by the server, if the remote version has changed in the meantime,
185+ * for example from `white` to `red`. This will lead to a change event with
186+ * origin `conflict`, usually a few seconds after the event with origin
187+ * `window` . Note that since you already changed it from `white` to `blue` in
188+ * the local version a few seconds ago, `oldValue` is now your local value of
189+ * `blue`:
190190 *
191191 * ```js
192192 * {
@@ -212,11 +212,6 @@ function getModuleNameFromBase(path: string): string {
212212 *
213213 * If there is an algorithm to merge the differences between local and remote
214214 * versions of the data, conflicts may be automatically resolved.
215- * {@link storeObject} or {@link storeFile} must not be called synchronously from
216- * the change event handler, nor by chaining Promises. {@link storeObject} or
217- * {@link storeFile} must not be called until the next iteration of the JavaScript
218- * Task Queue, using for example
219- * [`setTimeout()`](https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout).
220215 *
221216 * If no algorithm exists, conflict resolution typically involves displaying local
222217 * and remote versions to the user, and having the user merge them, or choose
0 commit comments