From 2b5899fdf1dd37846dfee0106b3fb6b412e593ea Mon Sep 17 00:00:00 2001
From: Marc Rousavy <me@mrousavy.com>
Date: Mon, 7 Oct 2024 23:07:33 +0200
Subject: [PATCH] docs: More precise base methosd

---
 docs/docs/hybrid-objects.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/hybrid-objects.md b/docs/docs/hybrid-objects.md
index e6b321c9c..07f24ea2d 100644
--- a/docs/docs/hybrid-objects.md
+++ b/docs/docs/hybrid-objects.md
@@ -63,7 +63,7 @@ interface ImageFactory extends HybridObject {
 
 ## Base Methods
 
-Every Hybrid Object has base methods and properties:
+Every Hybrid Object has base methods and properties, like `name`, `toString()` and `equals(..)`:
 
 ```ts
 const math = NitroModules.createHybridObject<Math>("Math")
@@ -76,7 +76,7 @@ console.log(math.equals(anotherMath)) // true
 
 ### `dispose()`
 
-Every Hybrid Object has a `dispose()` method.
+Additionally, every Hybrid Object has a `dispose()` method.
 Usually, you should not need to manually dispose Hybrid Objects as the JS garbage collector will delete any unused objects anyways.
 Also, most Hybrid Objects in Nitro are just statically exported singletons, in which case they should never be deleted throughout the app's lifetime.