Updates to fsi tenancy markdown including additional copy blocks

oci-generative-ai-agents-fsi/2-setup/setup-tenancy.md

@@ -81,7 +81,20 @@ In order to facilitate those permissions, we will create a Dynamic Group which w
    ![Screenshot showing how to navigate to the dynamic groups section](./images/dynamic-group-navigation.png)
 
 1. Name the dynamic group: _oci-genai-agents-service_
+
+    ```text
+      <copy>
+      oci-genai-agents-service
+      </copy>
+      ```
 1. Provide an optional description (example: `This group represents the OCI Generative AI Agents service`)
+
+      ```text
+      <copy>
+      This group represents the OCI Generative AI Agents service
+      </copy>
+      ```
+
 1. Select the **Match any rules defined below** option in the **Matching rules** section.
 1. Enter the following expression in the **Rule 1** textbox:
 
@@ -108,7 +121,21 @@ Next, we will create the access policies:
    ![Screenshot showing how to initiate the creation of a new policy](./images/create-new-policy-navigation.png)
 
 1. Provide a name for the policy (example: _oci-generative-ai-agents-workshop_).
+
+      ```text
+      <copy>
+      oci-generative-ai-agents-workshop
+      </copy>
+      ```
+
 1. Provide a description (example: _OCI Generative AI Agents Hands-On-Lab Policy_).
+
+      ```text
+      <copy>
+      OCI Generative AI Agents Hands-On-Lab Policy
+      </copy>
+      ```
+
 1. Make sure that the root compartment is selected.
 1. Enable the **Show manual editor** option.
 1. In the **Policy Builder** textbox, enter the following policy statements:

oci-generative-ai-agents-fsi/3-setup-the-database/setup-the-database-tenancy.md

@@ -38,7 +38,21 @@ In this task we are going to create a new ADB instance.
    ![Screenshot showing how to navigate to the create ADB page](./images/create-adb-button.png)
 
 1. For the **Display name** use: _loan-compliance_.
+
+   ```text
+      <copy>
+      loan-compliance
+      </copy>
+      ```
+
 1. For the **Database name** use: _loancompliance_.
+
+   ```text
+      <copy>
+      loancompliance
+      </copy>
+      ```
+
 1. Under the **Compartment**, make sure that the **root** compartment is selected.
 1. Under **Workload type** make sure that **Data Warehouse** is selected.
 
@@ -302,6 +316,13 @@ In this task we are going to create a Vault and an encryption key. We are going
 
 1. Under the **Create in Compartment**, make sure that the **root** compartment is selected.
 1. For the **Name** field use: _loan-compliance-secrets_
+
+   ```text
+      <copy>
+      loan-compliance-secrets
+      </copy>
+      ```
+
 1. Click the **Create Vault** button at the bottom of the form.
 
    ![Screenshot showing how to create the vault](./images/create-vault.png)
@@ -318,6 +339,13 @@ In this task we are going to create a Vault and an encryption key. We are going
 
 1. Under the **Create in Compartment**, make sure that the **root** compartment is selected.
 1. For the **Name** field use: _loan-compliance-key_
+
+     ```text
+      <copy>
+      loan-compliance-key
+      </copy>
+      ```
+
 1. Click the **Create Key** button.
 
    ![Screenshot showing details for creating an encryption key](./images/create-key-details.png)
@@ -338,6 +366,13 @@ In this section we are going to create a connection to our database. This connec
    ![Screenshot showing how to navigate to the create vault page](./images/create-connection-button.png)
 
 1. For the **Name** field use: _loan-compliance_
+
+   ```text
+      <copy>
+      loan-compliance
+      </copy>
+      ```
+
 1. Under the **Compartment**, make sure that the **root** compartment is selected.
 1. Make sure that the **Select database** option is selected under the **Database details** section.
 1. In the **Database cloud service** drop-down, select **Oracle Autonomous Database**.
@@ -353,6 +388,13 @@ In this section we are going to create a connection to our database. This connec
    This step will create a secret which will be stored in the Vault created earlier and will contain the password for connecting to the database.
 
 1. For the **Name** field use: _loan-compliance-admin-password_
+
+   ```text
+      <copy>
+      loan-compliance-admin-password
+      </copy>
+      ```
+
 1. Select the **loan-compliance-secrets** in the **Valut in...** drop-down.
 1. Select the **loan-compliance-key** in the **Encryption key in...** drop-down.
 1. In the **User password** field, type the password you've used when you created the ADB instance.
@@ -370,6 +412,13 @@ In this section we are going to create a connection to our database. This connec
    ![Screenshot showing how to create the ](./images/create-connection-5.png)
 
 1. For the **Name** field use: _loan-compliance-wallet-secret_
+
+   ```text
+      <copy>
+      loan-compliance-wallet-secret
+      </copy>
+      ```
+
 1. Select the **loan-compliance-secrets** in the **Valut in...** drop-down.
 1. Select the **loan-compliance-key** in the **Encryption key in...** drop-down.
 1. Under the **Wallet** section, select the **Retrieve regional wallet from Autonomous Database** option.

oci-generative-ai-agents-fsi/4-create-the-agent/create-the-agent-sandbox.md

@@ -21,6 +21,10 @@ This lab assumes you have:
 
 ## Task 1: Create the agent
 
+1. In the OCI Console, click the **Region** selector in the top-right corner and switch to **US Midwest (Chicago)** for this workshop.
+
+   ![Changing Region](./images/chicagoregion.png)
+
 1. Click the navigation menu on the top left.
 1. Click **Analytics & AI**.
 1. Click **Generative AI Agents**.
@@ -33,10 +37,31 @@ This lab assumes you have:
 
    ![Screenshot showing how to create a new agent](./images/create-new-agent-tenancy.png)
 
-1. For the **Name** field use: _loan compliance agent_
+1. For the **Name** field use: 
+
+      ``` text
+      <copy>
+      loan compliance agent
+      </copy>
+      ```
+
 1. For the **Compartment** field, make sure that your compartment is selected.
-1. For the **Description** field, use: _This agent assists compliance officers in reviewing applications, workloads, and policy compliance_.
-1. For the **Welcome message** field, use: _Hello! I’m your compliance assistant. How can I help?_
+1. For the **Description** field, use:
+
+      ``` text
+      <copy>
+      This agent assists compliance officers in reviewing applications, workloads, and policy compliance
+      </copy>
+      ```
+
+1. For the **Welcome message** field, use:
+
+      ``` text
+      <copy>
+      Hello! I’m your compliance assistant. How can I help?
+      </copy>
+      ```
+
 1. Click the **Next** button.
 
    ![Screenshot showing the basic information for the agent](./images/basic-agent-info-sandbox.png =50%x*)
@@ -49,7 +74,20 @@ This lab assumes you have:
 
 1. Select the **RAG** tool option.
 1. Under the **RAG Configuration** section, use _Knowledge base loan policy articles_ in the **Name** field.
-1. For the **Description** field, use: _Retrieves lending policy manuals and underwriting rules (DTI, credit score thresholds, FHA/VA limits, manual underwriting guidance)_.
+
+      ``` text
+      <copy>
+      Knowledge base loan policy articles
+      </copy>
+      ```
+
+1. For the **Description** field, use: 
+
+      ``` text
+      <copy>
+      Retrieves lending policy manuals and underwriting rules (DTI, credit score thresholds, FHA/VA limits, manual underwriting guidance)
+      </copy>
+      ```
 
    It is very important to provide a high-level description of the knowledge that this tool can retrieve. This allows the agent to make accurate decisions when choosing to invoke this tool.
 
@@ -61,6 +99,13 @@ This lab assumes you have:
    ![Screenshot showing more configuration for the RAG tool](./images/rag-tool-info-2-sandbox.jpg)
 
 1. In the **New knowledge base** form, use: _Compliance officer knowledge base loan policy articles_ for the **Name** field.
+
+      ``` text
+      <copy>
+      Compliance officer knowledge base loan policy articles
+      </copy>
+      ```
+
 1. Make sure that your compartment is selected in the **Compartment** field.
 1. In the **Data store type** field, we will select **Object storage** to be able to retrieve information from our storage bucket.
 1. Make sure that **Enable hybrid search** is checked. Enabling this option instructs the system to combine lexical and semantic search when scanning our documents.
@@ -69,6 +114,13 @@ This lab assumes you have:
    ![Screenshot showing the knowledge base configuration](./images/knowledge-base-info-1-sandbox.png)
 
 1. In the **Specify data source** form, use: _loan policy docs_ for the **Name** field.
+
+      ``` text
+      <copy>
+      loan policy docs
+      </copy>
+      ```
+
 1. Make sure that the **Enable multi-modal parsing** option is **not** checked. This option enables parsing of rich content, such as charts and graphics, to allow responses based on visual elements. However, we do not have any images in our knowledge articles so right now this option is not required.
 1. Under the **Data bucket** option, select the _loan-policy-manuals_ bucket into which we've previously uploaded the knowledge articles PDF files.
 1. Check the **Select all in bucket option**. This option will automatically flag all of the file in the bucket for ingestion instead of us having to select each file individually.
@@ -97,8 +149,21 @@ This lab assumes you have:
    ![Screenshot showing the create tool button for creating the SQL tool](./images/create-new-tool.png)
 
 1. Click the **SQL** option.
-1. For the **Name** field, use: _Loan Applications database_.
-1. For the **Description** field, use: _Tables contain applicants, loan applications, statuses, and officers for compliance review._
+1. For the **Name** field, use
+
+       ``` text
+      <copy>
+      Loan Applications database
+      </copy>
+      ```
+
+1. For the **Description** field, use:
+
+      ``` text
+      <copy>
+      Tables contain applicants, loan applications, statuses, and officers for compliance review
+      </copy>
+      ```
 
    ![Screenshot showing the initial set of the SQL tool configuration](./images/sql-tool-info-1.png)
 
@@ -190,8 +255,9 @@ This lab assumes you have:
 
 1. For **Model customization**, select the **Small** option.
 1. For **Dialect**, select **Oracle SQL**.
-1. In the **Database tool connection in...** select the **connection-loancomplianceXXXX** connection we've previously created.
-   >💡 _If your database tool connection does not appear (“Option not available”), select Cancel and re-add the SQL tool by repeating Task 3: Add the SQL Tool_
+1. In the **Database tool connection**, select _your compartment_, then choose the **connection-loancomplianceXXXX** connection we previously created.
+
+   >💡 _If your database tool connection does not appear in your compartment (“Option not available”), select Cancel and re-add the SQL tool by repeating Task 3: Add the SQL Tool._
 
 13. Click the **Test connection** button. You should see a successful connection attempt.
 14. Enable the **SQL execution** option. This option will instruct the tool to execute the SQL queries generated by the tool as a result of the user's requests. This will allow the agent to craft intelligent responses based on the data returned from the queries.

oci-generative-ai-agents-fsi/4-create-the-agent/create-the-agent-tenancy.md

@@ -36,9 +36,30 @@ This lab assumes you have:
    ![Screenshot showing how to create a new agent](./images/create-new-agent-tenancy.png)
 
 1. For the **Name** field use: _loan compliance agent_
+
+   ```text
+      <copy>
+      loan compliance agent
+      </copy>
+      ```
+
 1. For the **Compartment** field, make sure that your compartment is selected.
 1. For the **Description** field, use: _This agent assists compliance officers in reviewing applications, workloads, and policy compliance_.
+
+   ```text
+      <copy>
+      This agent assists compliance officers in reviewing applications, workloads, and policy compliance.
+      </copy>
+      ```
+
 1. For the **Welcome message** field, use: _Hello! I’m your compliance assistant. How can I help?_
+
+   ```text
+      <copy>
+      Hello! I'm your compliance assistant. How can I help?
+      </copy>
+      ```
+
 1. Click the **Next** button.
 
    ![Screenshot showing the basic information for the agent](./images/basic-agent-info-sandbox.png =50%x*)
@@ -51,8 +72,21 @@ This lab assumes you have:
 
 1. Select the **RAG** tool option.
 1. Under the **RAG Configuration** section, use _Knowledge base loan policy articles_ in the **Name** field.
+
+   ```text
+      <copy>
+      Knowledge base loan policy articles
+      </copy>
+      ```
+
 1. For the **Description** field, use: _Retrieves lending policy manuals and underwriting rules (DTI, credit score thresholds, FHA/VA limits, manual underwriting guidance)_.
 
+   ```text
+      <copy>
+      Retrieves lending policy manuals and underwriting rules (DTI, credit score thresholds, FHA/VA limits, manual underwriting guidance).
+      </copy>
+      ```
+
    It is very important to provide a high-level description of the knowledge that this tool can retrieve. This allows the agent to make accurate decisions when choosing to invoke this tool.
 
    ![Screenshot showing the initial configuration for the RAG tool](./images/rag-tool-info-1.png)
@@ -63,6 +97,13 @@ This lab assumes you have:
    ![Screenshot showing more configuration for the RAG tool](./images/rag-tool-info-2-sandbox.jpg)
 
 1. In the **New knowledge base** form, use: _Compliance officer knowledge base loan policy articles_ for the **Name** field.
+
+   ```text
+      <copy>
+      Compliance officer knowledge base loan policy atricles
+      </copy>
+      ```
+
 1. Make sure that your compartment is selected in the **Compartment** field.
 1. In the **Data store type** field, we will select **Object storage** to be able to retrieve information from our storage bucket.
 1. Make sure that **Enable hybrid search** is checked. Enabling this option instructs the system to combine lexical and semantic search when scanning our documents.
@@ -71,6 +112,13 @@ This lab assumes you have:
    ![Screenshot showing the knowledge base configuration](./images/knowledge-base-info-1-sandbox.png)
 
 1. In the **Specify data source** form, use: _loan policy docs_ for the **Name** field.
+
+   ```text
+      <copy>
+      loan policy docs
+      </copy>
+      ```
+
 1. Make sure that the **Enable multi-modal parsing** option is **not** checked. This option enable parsing of rich content, such as charts and graphics, to allow responses based on visual elements. However, we do not have any images in our knowledge articles so right now this option is not required.
 1. Under the **Data bucket** option, select the _loan-policy-manuals_ bucket into which we've previously uploaded the knowledge articles PDF files.
 1. Check the **Select all in bucket option**. This option will automatically flag all of the file in the bucket for ingestion instead of us having to select each file individually.
@@ -84,7 +132,7 @@ This lab assumes you have:
 
    ![Screenshot showing the knowledge base configuration](./images/knowledge-base-info-2.png)
 
-1. The knowledge base will take a few minutes to create and ingest the data.
+1. The knowledge base will take a few minutes to create and ingest the data. You may proceed to the next step while the knowledge base provisions.
 1. Back at the **Add knowledge bases** panel, make sure that the checkbox next to the knowledge base name is checked.
    >💡 _If your knowledge base does not appear (“No items found”), you can still continue to the next step. The knowledge base is already selected and provisioning in the background. You may open a new tab and navigate to Agents > Knowledge Bases to confirm it is provisioning._
 
@@ -100,8 +148,21 @@ This lab assumes you have:
 
 1. Click the **SQL** option.
 1. For the **Name** field, use: _Loan Applications database_.
+
+   ```text
+      <copy>
+      Loan Applications database.
+      </copy>
+      ```
+
 1. For the **Description** field, use: _Tables contain applicants, loan applications, statuses, and officers for compliance review._.
 
+   ```text
+      <copy>
+      Tables contain applicants, loan applications, statuses, and officers for compliance review.
+      </copy>
+      ```
+
    ![Screenshot showing the initial set of the SQL tool configuration](./images/sql-tool-info-1.png)
 
 1. Under **Import database schema configuration for this tool**, selec the **Inline** option which will allow us to use the same schema text we've used when we created the database.
@@ -150,7 +211,7 @@ This lab assumes you have:
       );
       </copy>
       ```
-
+1. Under the **in-context learning examples**, leave the **None** option selected.
 1. Under the **Description of tables and columns**, select the **Inline** option.
 1. Copy and paste the following text into the **Description of tables and columns**. This verbal description contains details about each table and column. This will allow the tool to better understand the data stored in our database:
 
@@ -192,7 +253,7 @@ This lab assumes you have:
 
 1. For **Model customization**, select the **Small** option.
 1. For **Dialect**, select **Oracle SQL**.
-1. In the **Database tool connection in...** select the **connection-loancomplianceXXXX** connection we've previously created.
+1. In the **Database tool connection**, select your compartment, then choose the **connection-loancomplianceXXXX** connection we've previously created.
    >💡 _If your database tool connection does not appear (“Option not available”), select Cancel and re-add the SQL tool by repeating Task 3: Add the SQL Tool_
 
 13. Click the **Test connection** button. You should see a successful connection connection attempt.