From 1c5b94f5e3f1d79d302d80e949998cbc4d42396f Mon Sep 17 00:00:00 2001
From: Michael <59754757+drazzilb91@users.noreply.github.com>
Date: Fri, 22 Dec 2023 20:16:26 +0000
Subject: [PATCH] Clarified key to use when releasing attributes

---
 docs/guide/write_client.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guide/write_client.md b/docs/guide/write_client.md
index 92043f9..05c7437 100644
--- a/docs/guide/write_client.md
+++ b/docs/guide/write_client.md
@@ -287,7 +287,7 @@ On the other hand, let's imagine we're writing a client for updating manually en
 
 ### Releasing attributes
 
-If we don't want to own an attribute any more, we can release it too. This will give up ownership to another service the user has connected that can fill it, or otherwise disable the attribute. The release call looks just like acquiring, except we send our array of JSON objects to `https://exist.io/api/2/attributes/release/`.
+If we don't want to own an attribute any more, we can release it too. This will give up ownership to another service the user has connected that can fill it, or otherwise disable the attribute. The release call looks just like acquiring, except we use the `name` key (even if we used `template` to acquire the attribute) and we send our array of JSON objects to `https://exist.io/api/2/attributes/release/`.
 
 ## Creating a new attribute