Removing code snippets, references, and procedures

Author: Cristian-Venticinque

modules/ROOT/pages/_partials/acb-component-info.adoc

@@ -234,19 +234,11 @@ The configuration XML file now includes the XML for the HTTP Listener within the
 
 </flow>
 ----
-. Add another component, this time using the XML configuration menu.
+. Add another component, this time using the configuration XML.
 +
-For example, add the `<http:listener-config/>` component from a snippet.
+In the configuration XML, place your cursor before the opening `<flow>` tag. Ensure that the cursor is not inside the `<flow/>` element. Add the following code:
 +
-.. In the configuration XML, place your cursor before the opening `<flow>` tag, and type `http`.
-+
-Ensure that the cursor is not inside the `<flow/>` element.
-+
-.. Type `http`, and select the `http:listener-config` snippet:
-+
-image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config snippet highlighted in the configuration XML menu"]
-+
-The snippet adds the following code:
+// image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the configuration XML menu"]
 +
 [source,xml]
 ----

modules/ROOT/pages/af-project-files.adoc

@@ -1145,7 +1145,7 @@ The `ref` element is used in different elements in the agent network YAML, and i
 
 The `ref` element represents another asset that exists in Exchange. The type of asset referenced depends on the context (such as agent, MCP server, LLM provider). The semantic is always that of referencing an asset that exists in Exchange, or will exist when the agent network is published (meaning, it's defined in the file). If referenced, it's in the `dependencies` section of `exchange.json`.
 
-This snippet represents a link to an HR agent. The `name` attribute doesn't point to the agent's human friendly or logical name (which can change); instead, it references the `assetId` that `hr-agent` has in Exchange.
+This example represents a link to an HR agent. The `name` attribute doesn't point to the agent's human friendly or logical name (which can change); instead, it references the `assetId` that `hr-agent` has in Exchange.
 
 [source,yaml]
 ----

modules/ROOT/pages/int-ai-gen-flow-examples.adoc

@@ -71,7 +71,7 @@ After reviewing and inserting the generated flow into your project:
 ----
 +
 This example flow is configured to poll for new cases every 5000 milliseconds.
-. Use built-in snippets to add configurations for your Salesforce instance and email inbox.
+. Add the required configurations for your Salesforce instance and email inbox in your configuration XML.
 
 The following is an example of the completed flow:
 
@@ -165,7 +165,7 @@ The `type` attribute is set to `Account` to specify the object type to update.
 
 === Complete the Flow 
 
-To run this flow,add configurations for your Salesforce instance.
+To run this flow, add the required configurations for your Salesforce instance in your configuration XML.
 
 The following is an example of the completed flow:
 
@@ -265,7 +265,7 @@ output application/java
 After reviewing and inserting the generated flow into your project:
 
 . Update the name of the database table and fields to match what is configured in your MySQL database. 
-. To run this flow, use built-in snippets to add configurations for your Salesforce instance.
+. To run this flow, add the required configurations for your Salesforce instance in your configuration XML.
 
 The following is an example of a completed flow:
 
@@ -372,7 +372,7 @@ After reviewing and inserting the generated flow into your project:
 . Update the `watermarkColumn` in the Database *Listener* to whichever database column is used to indicate new records. 
 +
 The values that are taken from this column are used to filter the contents of the next poll, so that only rows with a greater watermark value are processed.
-. To run this flow, use built-in snippets to add configurations for your database and email inbox.
+. To run this flow, add the required configurations for your database and email inbox in your configuration XML.
 
 The following is an example of the completed flow:
 

modules/ROOT/pages/int-create-secure-configs.adoc

@@ -391,11 +391,9 @@ The POM file includes dependencies for the components in the configuration XML.
 
 To use an encrypted value in a Mule application: 
 
-. Before the `<flow/>` element in the configuration XML, add the Secure Configuration Properties _snippet_ (`<secure-properties:config/>`) by pressing Cmd+Space (Mac) or Ctrl+Space (Windows), typing the initial letters of the element name, such as `secu`, and then selecting the snippet:
+. Before the `<flow/>` element in the configuration XML, add the following Secure Configuration Properties configuration (`<secure-properties:config/>`):
 +
-image::acb-snippet-secure-config-prop.png["Selecting Secure Configuration Properties Snippet"]
-+
-The XML for an unmodified snippet looks like this before a `<flow/>` element:
+// image::acb-snippet-secure-config-prop.png["Selecting Secure Configuration Properties"]
 +
 [source,xml]
 ----
@@ -409,12 +407,10 @@ The XML for an unmodified snippet looks like this before a `<flow/>` element:
 ...
 ----
 +
-The snippet preconfigures parts of the element that the basic XML configuration does not, so be sure to select the _snippet_ and _not_ the basic XML for this element, which has the same name but a different icon. Like all snippets, this snippet is identified by a two-dimensional box icon, while the basic XML for this element has a three-dimensional box icon. 
-+
-When you _first_ add the `<secure-properties:config/>` snippet to the configuration XML, you can tab to the `algorithm` attribute to select another algorithm, or you can change the value manually:
+. Optionally change the `algorithm` attribute to select another algorithm:
 +
 image::int-secure-config-algorithms.png["List of supported algorithms in Secure Configuration Properties module."]
-. Configure the snippet with values for the `file`, `key`, and `algorithm` attributes, for example:
+. Configure the element with values for the `file`, `key`, and `algorithm` attributes, for example:
 +
 [source,xml]
 ----
@@ -431,7 +427,7 @@ If you want to use the variable `$\{env}` in your filename configuration, see <<
 * `name`: A name of your choice for the encryption key (defaults to `${encryption.key}`) 
 +
 This name serves as the key for the encryption value (password) used to encrypt your secure properties with the Secure Properties Tool.
-* `algorithm`: Algorithm you used to encrypt your secure properties (defaults to Blowfish in the snippet). Other <<algorithms, algorithms>> are available.
+* `algorithm`: Algorithm you used to encrypt your secure properties (defaults to Blowfish in the previous example). Other <<algorithms, algorithms>> are available.
 . In the connector or component XML, add the key of an encrypted property as the value of an XML attribute, for example:
 +
 [source,xml]
@@ -510,7 +506,7 @@ Before you begin:
 
 To hide sensitive values from the Runtime Manager UI when you deploy to CloudHub or CloudHub 2.0: 
 
-. In the `mule-artifact.json` file for your application, provide the _name_ of the encryption key (`encryption.key` by default) that you provided in the global `<secure-properties:config/>` snippet within your configuration XML, for example:
+. In the `mule-artifact.json` file for your application, provide the _name_ of the encryption key (`encryption.key` by default) that you provided in the global `<secure-properties:config/>` element within your configuration XML, for example:
 +
 ----
 {

modules/ROOT/pages/tut-af-integrate-connect-to-a-db.adoc

@@ -70,13 +70,8 @@ image::add-mysql-driver-dependency.png["pom.xml with new dependency highlighted"
 == Add a Database Connector Configuration
 
 . In Anypoint Code Builder, open `american-ws-anypoint-code-builder.xml`.
-. In the configuration XML, add the global `<db:config/>` snippet.
-.. Place your cursor before the opening <flow> tag.
-.. Press Ctrl+Spacebar (Mac) or Cmd+Spacebar (Windows).
-.. Type `mysql` to search for the snippet.
-.. Select the snippet `db:mysql-config`.
+. In the configuration XML, add the following global `<db:config/>` configuration before the opening <flow> tag:
 +
-.Snippet XML before the opening <flow> tag:
 [source,xml]
 ----
 <db:config name="Mysql_Database_Config" >
@@ -131,7 +126,7 @@ NOTE: The `getFlights` flow contains an expected error: `The content of element
 . Add the *Select* operation for Anypoint Connector for Database (Database Connector).
 +
 Either search for *Select* or navigate to the operation from *Connectors* > *Database* > *Select*.
-. Provide this configuration for the snippet:
+. Provide this configuration for the Select operation:
 +
 [tabs]
 ====

modules/ROOT/pages/tut-graphql-test-first-implementation.adoc

@@ -44,7 +44,7 @@ curl --request POST \
 If you receive the error `curl: (7) Failed to connect to localhost port 8081 after 0 ms: Couldn't connect to server`, stop and rerun the application in debug mode. For guidance with stopping the application, see xref:int-debug-mule-apps.adoc[].
 +
 TIP: Tools such as Postman provide a way to build GraphQL queries. For example, 
-in Postman, you can place your query in the *Body* tab and find the code snippet for a `curl` request. The resulting command includes newline (`\\n`) and tab (`\\t`) characters that you can delete from the `curl` command's `--data` value. For more information, see https://learning.postman.com/docs/sending-requests/graphql/graphql-http/[Make an HTTP call with GraphQL] in the Postman documentation.
+in Postman, you can place your query in the *Body* tab and copy the example `curl` request. The resulting command includes newline (`\\n`) and tab (`\\t`) characters that you can delete from the `curl` command's `--data` value. For more information, see https://learning.postman.com/docs/sending-requests/graphql/graphql-http/[Make an HTTP call with GraphQL] in the Postman documentation.
 +
 Anypoint Code Builder returns the following output in the terminal (manually reformatted to enhance readability):
 +

modules/ROOT/pages/tut-slack-create-config-files-sfdc.adoc

@@ -37,34 +37,50 @@ email:
 slack:
  token: "yourSlackToken"
 --
-. Navigate to your `new-case-salesforce.xml` file, add a new line before the `</mule>` tag, type `configuration` and select *mule:configurationProperties*:
+. Navigate to your `new-case-salesforce.xml` file, add a new line before the `</mule>` tag, and paste this line:
 +
-image::select-mule-config-properties-contacts-sync.png["Code snippet with *mule:configurationProperties* highlighted in search results"]
+[source,XML]
+--
+<configuration-properties file="config.yaml" doc:name="Configuration properties" />
+--
+// image::select-mule-config-properties-contacts-sync.png["Code snippet with *mule:configurationProperties* highlighted in search results"]
+
+////
 . Scroll through the attributes and set the value of `file` to `config.yaml`:
 +
 [source,XML]
 --
 <configuration-properties file="config.yaml" doc:name="Configuration properties" />
 --
+////
 
 == Configure Your Salesforce Connector
 
 Use the values in your `config.yaml` file to connect the Salesforce Connector to your Salesforce environment:
 
-. In your `new-case-salesforce.xml` file, create a new line after the `<configuration-properties/>` element, type `salesforce`, and select *salesforce:sfdc-config*:
+. In your `new-case-salesforce.xml` file, create a new line after the `<configuration-properties/>` element, and paste the following code:
 +
-image::sync-api-select-sfdc-config.png["Code snippet with *Salesforce:sfdc-config* highlighted in search results"]
-. Set the *name* field to `Salesforce-Config`.
-. Create a new line, type `basic` and select *Salesforce:Basic*:
-+
-image::basic-auth-sfdc-connector.png["Code snippet with *Salesforce:basic* highlighted in search results"]
-. Configure the `username` and `password` properties to use your configuration file values:
+[source,XML]
+--
+<salesforce:sfdc-config name="Salesforce-Config" doc:name="Config">
+ <salesforce:basic-connection username="${salesforce.username}" password="${salesforce.password}" />
+</salesforce:sfdc-config>
+--
+
+// image::sync-api-select-sfdc-config.png["Code snippet with *Salesforce:sfdc-config* highlighted in search results"]
+// . Set the *name* field to `Salesforce-Config`.
+// . Create a new line, type `basic` and select *Salesforce:Basic*:
+//+
+// image::basic-auth-sfdc-connector.png["Code snippet with *Salesforce:basic* highlighted in search results"]
+//. Configure the `username` and `password` properties to use your configuration file values:
 +
+////
 [source,XML]
 --
 <salesforce:basic-connection username="${salesforce.username}" password="${salesforce.password}" securityToken="${salesforce.token}" />
 --
 +
+////
 [NOTE]
 --
 When you move your cursor over the `${salesforce.username}` and `${salesforce.password}` elements, Anypoint Code Builder shows the values from the configuration file.
@@ -95,7 +111,7 @@ If you get an error, verify the error message to troubleshoot further.
 * `objectType`: *Case*
 * `config-ref`: *Salesforce-Config*
 * `name`: *On New Case*
-. In the `<salesforce:new-object-listener/>` element, replace `<scheduling-strategy/>` with the following snippet:
+. In the `<salesforce:new-object-listener/>` element, replace `<scheduling-strategy/>` with the following XML:
 +
 [source,XML]
 --
@@ -112,7 +128,7 @@ image::add-logger-end-flow-canvas.png["The flow canvas with the *Add Flow* plus
 +
 image::drag-logger-canvas.png["A workflow with the *Logger* component added"]
 +
-A `logger` component is added to the `flow` snippet in the code editor. 
+A `logger` component is added to the flow in the code editor. 
 +
 . Replace the `logger` component in the code editor with the following:
 +