From 11e12b82b29a6f3c86c4f3043806fcaec49aa221 Mon Sep 17 00:00:00 2001
From: Dan Schultzer <1254724+danschultzer@users.noreply.github.com>
Date: Sat, 5 Aug 2023 13:36:58 -0700
Subject: [PATCH] Expand readme on key location

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 35b221db..1017c3a8 100644
--- a/README.md
+++ b/README.md
@@ -232,13 +232,13 @@ end
 If the Authorization Header was verified, you'll be able to retrieve the current resource owner or access token.
 
 ```elixir
-ExOauth2Provider.Plug.current_access_token(conn) # access the token in the default location
-ExOauth2Provider.Plug.current_access_token(conn, :secret) # access the token in the secret location
+ExOauth2Provider.Plug.current_access_token(conn) # access the token in the `:default` location
+ExOauth2Provider.Plug.current_access_token(conn, :custom) # access the token in the `:custom` location if set as `:key` option in `plug ExOauth2Provider.Plug.VerifyHeader`
 ```
 
 ```elixir
-ExOauth2Provider.Plug.current_resource_owner(conn) # Access the loaded resource owner in the default location
-ExOauth2Provider.Plug.current_resource_owner(conn, :secret) # Access the loaded resource owner in the secret location
+ExOauth2Provider.Plug.current_resource_owner(conn) # Access the loaded resource owner in the `:default` location
+ExOauth2Provider.Plug.current_resource_owner(conn, :custom) # Access the loaded resource owner in the `:secret` location if set as `:key` option in `plug ExOauth2Provider.Plug.VerifyHeader`
 ```
 
 ### Custom access token generator