From 6f0d927909b285c0b148bff1b69240ee7598f2fb Mon Sep 17 00:00:00 2001
From: Prof Darrel Francis <20881844+darrelfrancis@users.noreply.github.com>
Date: Mon, 6 May 2024 10:31:18 +0100
Subject: [PATCH] Update options-api-realtime-data.md

Currently the explanation for the reset is backwards, saying that you should send `true` if you want to `keep current value`. In fact, you should send `false` to keep the current value, and `true` to replace it with null.
---
 docs/guide/options-api-realtime-data.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guide/options-api-realtime-data.md b/docs/guide/options-api-realtime-data.md
index b2a647ae..94ae44f0 100644
--- a/docs/guide/options-api-realtime-data.md
+++ b/docs/guide/options-api-realtime-data.md
@@ -235,12 +235,12 @@ this.$databaseUnbind('user', () => ({ name: 'unregistered' }))
 ```
 
 ```js
-// default behavior
+// default behavior is to keep current value
 this.$firestoreUnbind('user')
 this.$firestoreUnbind('user', false)
 // this.user === { name: 'Eduardo' }
 
-// using a boolean value for reset to keep current value
+// if you send Boolean true in the reset parameter, the value will change to null
 this.$firestoreUnbind('user', true)
 // this.user === null