From ba13ed59f5ec5a2329c4d346274bc3312baa957a Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Fri, 15 Sep 2023 19:51:57 -0600
Subject: [PATCH] Relationship between `selected_resources` and `graph` context
 variable

---
 .../docs/reference/dbt-jinja-functions/selected_resources.md    | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/docs/reference/dbt-jinja-functions/selected_resources.md b/website/docs/reference/dbt-jinja-functions/selected_resources.md
index 80c4250b8d5..a927ec317ae 100644
--- a/website/docs/reference/dbt-jinja-functions/selected_resources.md
+++ b/website/docs/reference/dbt-jinja-functions/selected_resources.md
@@ -30,6 +30,8 @@ For a given run it will look like:
 ["model.my_project.model1", "model.my_project.model2", "snapshot.my_project.my_snapshot"]
 ```
 
+Each value corresponds to a key in the `nodes` object within the [graph](/reference/dbt-jinja-functions/graph) context variable.
+
 It can be used in macros in a `pre-hook`, `post-hook`, `on-run-start` or `on-run-end` 
 to evaluate what nodes are selected and trigger different logic whether a particular node
 is selected or not.