Remove delta sharing icons from diagrams in Set up live data sharing …

…between Oracle Databases using Cloud Links and PL/SQL APIs (#308)

* new lab

* Update manifest.json

* updates

* Update use-delta-sharing.md

* Update use-delta-sharing.md

* Update use-delta-sharing.md

* livelabs folder

* Update adw-dcat-integrate.md

* updates

* updates to Introduction lab

* Update introduction.md

* LiveLabs workshop version and other freetier changes

* Update introduction.md

* Update introduction.md

* livelabs and freetier changes

* Update load-analyze-json.md

* Update load-analyze-rest.md

* more changes

* more updates

* more updates

* Update adw-dcat-integrate.md

* changed shared with serverless as deployment type

* Update load-local-data.md

* update shared to serverless

* update adb-dcat workshop

* added new lab 12

* Update manifest.json

* added new folder with an .md file in it

Please work!

* more testing

* Delete introduction.md

* new workshop and labs wip

* update labs

* more updates

* more updates

* more updates

* updates

* more updates

* updates before review cycle

* Update endpoint.png

* Update setup-workshop-environment.md

* Update setup-workshop-environment.md

* more updates

* final update before review

* updates

* replacement code

* Update create-share-recipients.md

* Update create-share-recipients.md

* Update create-share-recipients.md

* Update create-share-recipients.md

* Update create-share-recipients.md

* Update create-share-recipients.md

* updates

* Update manifest.json

* folder rename

* added content to data studio folder

* Delete user-bucket-credential-diagram.png

* updates self-qa

* Update introduction.md

* remove extra text files

* Update introduction.md

* Update setup-workshop-environment.md

* Data Studio Workshop Changes

* changes to data studio workshop

* Update setup-workshop-environment.md

* adb changes

* Update recipient-diagram.png

* diagram change

* Update user-bucket-credential-diagram.png

* SME feedback

* Update create-share.md

* Nilay changes

* changes

* Update consume-share.md

* Anoosha's feedback

* Update consume-share.md

* updated 2 screens and a sentence

* minor changes

* deleted extra images and added doc references

* new ECPU changes

* more changes to data sharing workshops

* more changes to fork (data studio)

* more changes

* Marty's feedback

* Marty's feedback to plsql workshop too

* Update setup-workshop-environment.md

* Delete 7381.png

* workshop # 3 ADB set up

and a couple of minor typos in workshops 1 and 2

* changes to adb-dcat workshop

* more changes

* minor typos in all 4 workshops

* quarterly qa build data lake

* new lab 11 in build DL with ADW

* minor changes database actions drop-down list

* final changes to build data lake workshop

* AI updates

AI workshop updates

* ai workshop updates

* Update query-using-select-ai.md

* Update query-using-select-ai.md

* updates

* more updates

* Update query-using-select-ai.md

* more new updates to ai workshop

* Update query-using-select-ai.md

* a new screen capture

* push Marty's feedback to fork

Final changes.

* updates sandbox manifest

* updates

* restored sandbox manifest

* Update setup-environment.md

* updates after CloudWorld

* final updates to ai workshop (also new labs 4 and 5)

* marty's feedback

* incorporated feedback

* minor PR edits by Sarah

* removed steps 7 & 8 Lab 2 > Task 3 per Alexey

The customer asked to remove this as it's not a requirement for the bucket to be public.

* more changes

* more changes per Alexey

* Update load-os-data-public.md

* Quarterly QA

I added a new step per the PM's request in the Data Sharing PL/SQL workshop. I also made a minor edit (removed space) in the Data Lake workshop.

* more updates

* Quarterly QA changes

* Update consume-share.md

* minor edit based on workshop user

* quarterly qa November 2023

* Added new videos to the workshop

Replaced 3 old silent videos with new ones. Added two new videos.

* Adding important notes to the two data sharing workshops

Per the PM's request.

* folder structure only  push to production

This push and the PR later is to make sure the folder structure is in the production repo before I start development. Only 1 .md file and the workshops folder.

* typos

* cloud links workshop

* UPDATES

* Update query-view.png

* update

* minor updates to chat ai workshop (Fork)

* test clones

* test pr

* Alexey's feedback

* Update data-sharing-diagram.png

* sarah's edits

* changes to Data Load UI

* removed script causing ML issue

* Update load-local-data.md

* updates: deprecated procedure and new code

* updates and test

* more updates

* minor update

* testing using a building block in a workshop

* updates

* building blocks debugging

* Update manifest.json

* fixing issues

* Update manifest.json

* delete cleanup.md from workshop folder (use common file)

* use common cleanup.md instead of local cleanup.md

* test common tasks

* update data sharing data studio workshop

* Update create-recipient.png

* PM's 1 feedback

* quarterly qa

* missing "Lab 2" from Manifest

* always free note addition

added a note

* always free change

* Update setup-environment.md

* update manage and monitor workshop

* Folder structure for new data share workshop (plus introduction.md)

* Updated Load and Analyze from clone

* Data Lake minor changes from clone

* manage and monitor workshop

* Remove the lab from the workshop per Marty's request

* mark-hornick-feedback

* used marty's setup file

* replaced notebook with a new one

* updates to lab 6 of manage and monitor

* Update adb-auto-scaling.md

* Nilay's feedback

* Update adb-auto-scaling.md

* updates to second ai workshop

* note change

* Changes to Load and Analyze workshop (other minor changes too)

* quarterly qa

* Update diagrams per Alexey (remove delta share icon)

---------

Co-authored-by: Michelle Malcher <[email protected]>
Co-authored-by: Sarah Hirschfeld <[email protected]>

shared/adw-data-lake/setup-live-data-sharing-db-actions/setup-workshop-environment/setup-workshop-environment.md

@@ -47,7 +47,7 @@ See [Signing In to the Console](https://docs.cloud.oracle.com/en-us/iaas/Content
 
 2. On the **Sign In** page, select your tenancy, enter your username and password, and then click **Sign In**.
 
-   ![The blurred username and masked password are displayed on the OCI Sign in screen. The tenancy's name and username are blurred. The Sign In button is highlighted.](./images/sign-in.png " ")
+   ![The blurred username and masked password are displayed on the OCI Sign in screen. The tenancy's name and username are blurred. The Sign In button is highlighted.](./images/sign-in.png =50%x*)
 
        >**Note:** Based on the Multi-factor authentication setup for your account, provide authentication to sign into the account. In our example, we clicked **Allow** on the iphone based on our authentication setup. For more details, refer to the [Managing Multifactor Authentication](https://docs.oracle.com/en-us/iaas/Content/Identity/Tasks/usingmfa.htm) documentation.
 

shared/adw-data-lake/use-data-sharing-cloud-links-plsql/create-share-recipients/create-share-recipients.md

@@ -6,7 +6,7 @@ A data share recipient is an entity such as an individual, an institution, or a
 
 In this lab, as a data share provider, you will create and authorize a new recipient that will access the **`demo_live_share`** data share that you just published and the `custsales` table in this share. You will need the sharing ID that you saved from an earlier step.
 
-![Recipient flow.](images/recipient-diagram.png =70%x*)
+![Recipient flow.](images/recipient-diagram.png =60%x*)
 
 Estimated Time: 5 minutes
 

shared/adw-data-lake/use-data-sharing-cloud-links-plsql/create-user/create-user.md

@@ -4,7 +4,7 @@
 
 In this lab, you as the **`admin`**, you will create a **data share provider** user and grant this user the necessary role and privileges, and enable data sharing.
 
-![Create a user and grant roles and privileges](./images/create-user-privileges-diagram.png " ")
+![Create a user and grant roles and privileges](./images/create-user-privileges-diagram.png =65%x*)
 
 Estimated Time: 15 minutes
 
@@ -109,15 +109,15 @@ Autonomous Database comes with a predefined database role named `DWROLE`. This r
 
     Copy the value and paste it into your text editor file.
 
-    ![Paste the value into a text editor file](images/copy-value-text-editor.png)
+    ![Paste the value into a text editor file](images/copy-value-text-editor.png =70%x*)
 
 3. Log out of the **`ADMIN`** user. On the **Oracle Database Actions | SQL** banner, click the drop-down list next to the **`ADMIN`** user, and then select **Sign Out** from the drop-down menu. When prompted if you want to leave the site, click **Leave**.
 
     ![Log out of admin](images/logout-admin.png)
 
 4. Log in as the newly created user, **`share_provider`**. On the **Sign-in** page, enter **`share_provider`** as the username and **`DataShare4ADW`** as the password, and then click **Sign in**.
 
-    ![Log in as share_provider](images/login-share-provider.png)
+    ![Log in as share_provider](images/login-share-provider.png =50%x*)
 
     You are now logged in as the newly created **`share_provider`** user. On the Launchpad, click the **Development** tab, and then click the **SQL** tab.
 

shared/adw-data-lake/use-data-sharing-cloud-links-plsql/introduction/introduction.md

@@ -71,7 +71,7 @@ In this workshop, you will assume the responsibilities of several users. Initial
 
 **_In real use cases, there will be different users performing different responsibilities._**
 
-  ![The workshop users.](images/users-diagram.png)
+  ![The workshop users.](images/users-diagram.png =50%x*)
 
 ### How Does Cloud Links Data Sharing Work?
 
@@ -82,7 +82,7 @@ At the high level, sharing data using cloud links works as follows:
 * The recipient uses the share provider's id to discover the available data shares and tables.
 * The recipient subscribes to the data share provider, retrieves data from the data share, and creates a share link and a view using the data share table.
 
-  ![The data sharing overview.](images/data-sharing-diagram.png)
+  ![The data sharing overview.](images/data-sharing-diagram.png =65%x*)
 
 You may now proceed to the next lab.
 

shared/adw-data-lake/use-data-sharing-cloud-links-plsql/setup-workshop-environment/setup-workshop-environment.md

@@ -63,33 +63,33 @@ A Cloud Administrator can optionally create a compartment in your tenancy to hel
 
 1. Open the **Navigation** menu and click **Identity & Security**. Under **Identity**, click **Compartments**.
 
-       ![The Navigation menu is clicked. The navigation path to Compartments is displayed.](./images/navigate-compartment.png "Click the Navigation menu, and navigate to Compartments.")
+       ![The Navigation menu is clicked. The navigation path to Compartments is displayed.](./images/navigate-compartment.png =65%x*)
 
     For faster navigation, you can pin items that you use frequently. To pin an item, hover over the menu item and then click pin to the left of the item name.
 
-    ![An example on pinning an item such as Data Lake/Data Catalog for quicker access is shown.](./images/pin-items.png " ")
+    ![An example on pinning an item such as Data Lake/Data Catalog for quicker access is shown.](./images/pin-items.png =65%x*)
 
     The pinned item is displayed in the **Pinned** section of the **Home** tab the next time you use the Navigation menu.
 
-    ![An example that shows the Compartment item pinned.](./images/pinned-item.png " ")
+    ![An example that shows the Compartment item pinned.](./images/pinned-item.png =65%x*)
 
     The **Recently visited** section of the **Home** tab shows recently used navigation items.
 
     To quickly find navigation menu items, use the **Search** box.
 
 2. On the **Compartments** page, click **Create Compartment**.
 
-   ![The Compartments page is displayed. The Create Compartment button is highlighted.](./images/click-create-compartment.png " ")
+   ![The Compartments page is displayed. The Create Compartment button is highlighted.](./images/click-create-compartment.png =65%x*)
 
 3. In the **Create Compartment** dialog box, enter **`training-adw-compartment`** in the **Name** field and **`Training ADW Compartment`** in the **Description** field.
 
 4. In the **Parent Compartment** drop-down list, select your parent compartment, and then click **Create Compartment**.
 
-   ![On the completed Create Compartment dialog box, click Create Compartment.](./images/create-compartment.png " ")
+   ![On the completed Create Compartment dialog box, click Create Compartment.](./images/create-compartment.png =65%x*)
 
    The **Compartments** page is re-displayed and the newly created compartment is displayed in the list of available compartments.
 
-   ![The newly created compartment is highlighted with its status as Active.](./images/compartment-created.png " ")
+   ![The newly created compartment is highlighted with its status as Active.](./images/compartment-created.png =65%x*)
 
 ## Task 3: Create an Autonomous Data Warehouse Instance
 
@@ -104,7 +104,7 @@ A Cloud Administrator can optionally create a compartment in your tenancy to hel
        * **Display Name:** **`ADW-Data-Lake`**.
        * **Database Name:** **`TrainingADW`**.
 
-       ![The completed "Provide basic information for the Autonomous Database" section is displayed.](./images/adb-basic-info.png " ")
+       ![The completed "Provide basic information for the Autonomous Database" section is displayed.](./images/adb-basic-info.png =75%x*)
 
 5. In the **Choose a workload type** section, accept the **Data Warehouse** default selection.
 
@@ -152,7 +152,7 @@ A Cloud Administrator can optionally create a compartment in your tenancy to hel
        **Important:** Make a note of this _password_ as you will need it to perform later tasks.
        * **Confirm password:** Confirm your password.
 
-       ![The completed "Create administrator credentials" section is displayed.](./images/adb-admin-credentials.png " ")
+       ![The completed "Create administrator credentials" section is displayed.](./images/adb-admin-credentials.png =65%x*)
 
 10. In the **Choose network access** section, select the **Secure access from everywhere** option as the access type.