Add more detail to Auth sections to reflect changes I've been making

document-templates/credentials.md

@@ -49,13 +49,24 @@ This is a credential-only node. Refer to [Custom API operations](/integrations/c
 
 
 ## Using _Auth method_
+
+To configure this credential, you'll need:
+
+- _List of fields they'll need to fill out within n8n_
 
 _Link to product's docs for this auth method._
 
 _STOP AND THINK: does this node require a step by step? If authentication is easy to set up, or if this node isn't heavily used, consider leaving out the step by step to minimise maintenance._
 
 _IF NEEDED: Include a step by step guide to how to set up a particular type of authentication. If multiple auth methods are available, create a section for each. For example, the Asana credentials have two sections: one for OAuth and one for access token (/integrations/builtin/credentials/asana/)_
 
+<!-- IF OAUTH FOR CLOUD-HOSTED DOESN'T REQUIRE ANY SETUP, use the section below. Otherwise omit -->
+/// note | Note for n8n Cloud users
+You'll only need to enter the Credentials Name and select the **Connect my account** button in the OAuth credential to connect your _Name_ account to n8n.
+///
+
+Should you need to configure OAuth2 from scratch or need more detail on what's happening in the OAuth web flow, refer to the instructions in the [_Name_ Oauth documentation](){:target=_blank .external-link} to set up OAuth._
+
 <!-- 
 Add any other sections here. 
 You should include: quirks, pain points, complex topics that trip people up