edits

_snippets/integrations/predefined-credential-type-how-to.md

@@ -1,7 +1,7 @@
 To use a predefined credential type:
 
 1. Open your HTTP Request node, or add a new one to your workflow.
-2. In **Authentication**, select **Existing Credential Type**.
+2. In **Authentication**, select **Predefined Credential Type**.
 3. In **Credential Type**, select the API you want to use. 
 4. In **Credential for `<API name>`**, you can:
     1. Select an existing credential for that platform, if available.

docs/integrations/core-nodes/n8n-nodes-base.httpRequest.md

@@ -8,8 +8,8 @@ The HTTP Request node is one of the most versatile nodes in n8n. It allows you t
 
 ## Node Reference
 
-- **Authentication:** there are two options for authentication:
-	- Select **Existing Credential Type** to use predefined credential types. This allows you to perform custom operations with some APIs where n8n has a node for the platform. For example, n8n has an Asana node, and supports using your Asana credentials in the HTTP Request node. Refer to [Custom API operations](/integrations/custom-operations/) for more information.
+- **Authentication:** there are two options for authentication. n8n recommends using the **Predefined credential type** option when it's available. It offers an easier way to set up and manage credentials, compared to configuring generic credentials.
+	- Select **Predefined Credential Type**. This allows you to perform custom operations, without additional authentication setup. For example, n8n has an Asana node, and supports using your Asana credentials in the HTTP Request node. Refer to [Custom API operations](/integrations/custom-operations/) for more information.
 	- Select **Generic Credential Type** to set up authentication using one of the following methods:
 		- Basic Auth
 		- Digest Auth
@@ -18,8 +18,7 @@ The HTTP Request node is one of the most versatile nodes in n8n. It allows you t
 		- OAuth2
 		- None
 	
-	!!! note "Use existing credential type when possible"
-		n8n recommends using the **Existing credential type** option when it's available. It offers an easier way to set up and manage credentials, compared to configuring generic credentials.
+	
 
 - **Request Method:** Select the method to be used for the request:
 	- DELETE

docs/integrations/custom-operations.md

@@ -2,13 +2,13 @@
 
 n8n supplies hundreds of nodes, allowing you to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the [HTTP Request](/integrations/core-nodes/n8n-nodes-base.httpRequest/) node.
 
-One of the most complex parts of setting up API calls is managing authentication. To simplify this, n8n provides a way to use existing credential types (credentials associated with n8n nodes).
+One of the most complex parts of setting up API calls is managing authentication. To simplify this, n8n simplifies authentication for services with an existing node.
 
 ## Predefined credential types
 
-A predefined credential type is a credential associated with a particular platform. You can use predefined credential types instead of generic credentials in the HTTP Request node.
+A predefined credential type is a credential that already exists in n8n. You can use predefined credential types instead of generic credentials in the HTTP Request node.
 
-For example: you create an Asana credential, for use with the Asana node. Later, you want to perform an operation that isn't supported by the Asana node, using Asana's API. You can use your existing Asana credential in the HTTP Request node to perform the operation.
+For example: you create an Asana credential, for use with the Asana node. Later, you want to perform an operation that isn't supported by the Asana node, using Asana's API. You can use your existing Asana credential in the HTTP Request node to perform the operation, without additional authentication setup.
 
 ### Using predefined credential types