Add pointer to #317 for potential DAG flow usage

Author: simonrob

README.md

@@ -4,7 +4,7 @@ Transparently add OAuth 2.0 support to IMAP/POP/SMTP client applications, script
 
 ## Motivation and capabilities<a id="motivation-and-capabilities"></a>
 Email services that support IMAP, POP and/or SMTP access are increasingly requiring the use of OAuth 2.0 to authenticate connections, but not all clients support this method.
-This tool creates a simple local proxy that intercepts the traditional IMAP/POP/SMTP authentication commands and transparently replaces them with the appropriate SASL (X)OAuth 2.0 commands and credentials.
+This tool creates a local proxy that intercepts the traditional IMAP/POP/SMTP authentication commands and transparently replaces them with the appropriate SASL (X)OAuth 2.0 commands and credentials.
 Your email client can continue to use the `login` or `auth`/`authenticate` options, with no need to make it aware of OAuth's existence.
 The proxy works in the background with a menu bar/taskbar helper or as a headless system service, and is compatible with macOS, Windows and Linux.
 

emailproxy.config

@@ -166,10 +166,12 @@ documentation = Accounts are specified using your email address as the section h
 		attempts before the first valid login, pre-encrypting account entries is highly recommended. See the example
 		script at https://github.com/simonrob/email-oauth2-proxy/issues/61#issuecomment-1259110336.
 
-	- The proxy supports the device authorisation grant (DAG) OAuth 2.0 flow, which may better suit headless systems
-	(currently only known to be available for Office 365 / Outlook). To use this flow, set `oauth2_flow = device`. With
+	- The proxy supports the device authorisation grant (DAG) OAuth 2.0 flow (currently only known to be available for
+    Office 365 / Outlook), which may better suit headless systems. To use this flow, set `oauth2_flow = device`. With
 	this flow, the proxy receives authorisation responses directly from the service provider, so no `redirect_uri` is
-	needed. An example account configuration is given below.
+	needed. An example account configuration is given below. For additional customisation, the proxy modifications and
+	scripts demonstrated at https://github.com/simonrob/email-oauth2-proxy/pull/317 show how the DAG flow authorisation
+    message could be pushed to a separate device, which may be useful when running the proxy headless or without a GUI.
 
 	Gmail customisation:
 	- The proxy supports the use of service accounts with Gmail for Google Workspace (note: normal Gmail accounts do not