From 41bfff7ce9042f57c01d88d803bde9a0c18de28e Mon Sep 17 00:00:00 2001
From: Xoconoch <93692082+Xoconoch@users.noreply.github.com>
Date: Wed, 11 Jun 2025 11:45:43 -0600
Subject: [PATCH] Update callback_examples.md

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

diff --git a/docs/callback_examples.md b/docs/callback_examples.md
index c3c4080..ebacfa5 100644
--- a/docs/callback_examples.md
+++ b/docs/callback_examples.md
@@ -8,7 +8,7 @@ The data models in `deezspot/models/callback/` follow a specific naming conventi
 
 For example:
 
-*   `playlistTrackObject`: This represents a `playlist` object within a `track` reporting context. It's a simplified version of a full `playlistObject` and is used as the parent for a track being processed as part of a playlist operation.
+*   `playlistTrackObject`: This represents a `playlist` object within a `track` reporting context. It's a simplified version of a full `playlistObject` and is used as the parent for a track being processed as part of a playlist operation (more on what a "parent" is later).
 *   `artistAlbumTrackPlaylistObject`: This represents an `artist` object, nested within an `album` object, which is inside a `track` object that is part of a `playlist`. This shows the full hierarchy of contexts.
 
 ## `trackCallbackObject` Examples
@@ -884,4 +884,4 @@ The `done` status for a playlist includes a summary of all track operations.
       "spotify": "37i9dQZF1DX1rVvRgjX59F"
     }
   }
-} 
\ No newline at end of file
+}