update images and .md / formating

Author: peterrsongg

mtdrworkshop/backend/Readme.md mtdrworkshop/backend/backend.mdmtdrworkshop/backend/Readme.md renamed to mtdrworkshop/backend/backend.md

@@ -1,10 +1,34 @@
-# Backend
+# Deploy the Backend Docker Image to Kubernetes
 
 ## Introduction
 
-In this lab, you will build and deploy the pre-built Helidon Java Docker image to OKE, then configure the API Gateway to work with your application.
+In this lab, you will build and deploy the pre-built Helidon Java backend Docker image to OKE, then configure the API Gateway.
 
-Estimated time: ~25-minutes.
+Estimated time: 25 minutes
+
+Watch the video below for a quick walk through of the lab.
+
+[](youtube:Th7YCV6e8CE)
+
+### Understand the Java backend application
+
+As with most React applications (https://reactjs.org/), this application uses remote APIs to handle data persistence. The backend implements five REST APIs including:
+
+* Retrieving the current list of todo items
+* Adding a new todo item
+* Finding a todo item by its ID
+* Updating an existing todo item
+* Deleting a todo item
+
+The APIs are documented using Swagger at http://130.61.67.158:8780/swagger-ui/#/.
+
+The backend is implemented using the following Java classes (under ./backend/src/...):
+
+* Main.java: starts and configures the main entry points
+* ToDoItem.java: maps a Todo Item instance to and from the JSON document
+* ToDoItemStorage.java: stores the Todo item in a persistent store that is the Oracle Autonomous database
+* ToDoListAppService.java: implements the Helidon service and exposes the REST APIs
+![bcknd apis](images/Backend-APIs.png)
 
 ### Objectives
 
@@ -16,36 +40,17 @@ Estimated time: ~25-minutes.
 
 ### Prerequisites
 
-This lab requires the completion of lab 1 and the provision of the OCI components.
-
-### Understanding the Java/backend application
-
-As with most React applications (https://reactjs.org/), this application uses remote APIs to handle data persistence. The backend implements 5 REST APIs including:
-- Retrieving the current list of todo items
-- Adding a new todo item
-- Finding a todo item by its id
-- Updating an existing todo item
-- Deleting a todo item.
-
-The APIs are documented using Swagger @ http://130.61.67.158:8780/swagger-ui/#/
-
-The backend is implemented using the following Java classes (under ./backend/src/...):   
-- Main.java: starts and configure the main entry points.
-- ToDoItem.java: maps a Todo Item instance to/from JSON  document
-- ToDoItemStorage.java: stores the Todo item in a persistent store i.e., the Oracle Autonomous database
-- ToDoListAppService.java: implements the Helidon service and exposes the REST APIs
-
-  ![](images/Backend-APIs.png " ")
+* This lab requires the completion of the **Setup Dev Environment** tutorial and the provisioning of the Orace Cloud Infrastructure (OCI) components.
 
-## **Task 1**: Build and push the Docker images to the OCI Registry
+## Task 1: Build and Push the Docker Images to the OCI Registry
 
 The OCI Container Regisry is where your Docker images are managed. A container registry should have been created for you in Lab 1 in your compartment.
 
 1. Edit ./backend/src/main/java/com/oracle/todoapp/Main.java
 
     - Locate the following code fragment
 
-    ![](images/CORS-Main.png " ")
+    ![](images/cors-main.png " ")
     - Replace `eu-frankfurt-1` in  `"https://objectstorage.eu-frankfurt-1.oraclecloud.com"` with your region
 
     - Save the file
@@ -55,7 +60,9 @@ This will allow the appropriate object storage bucket to access your application
 2. Run `build.sh` script to build and push the helidon-se image into the repository
 
     ```
+    <copy>
     cd $MTDRWORKSHOP_LOCATION/backend
+    </copy>
     ./build.sh
     ```
   In a couple of minutes, you should have successfully built and pushed the images into the OCI repository.
@@ -64,81 +71,92 @@ This will allow the appropriate object storage bucket to access your application
     - Go to the Console, click the hamburger menu in the top-left corner and open
     **Developer Services > Container Registry**.
    
-   ![](psong_images/container_registry.png)
+   ![](images/container-registry.png)
 
-## **Task 2**: Deploy on Kubernetes and Check the Status
+## Task 2: Deploy on Kubernetes and Check the Status
 
 1. Run the `deploy.sh` script
 
   ```
+  <copy>
   cd $MTDRWORKSHOP_LOCATION/backend 
   ./deploy.sh
+  </copy>
   ```
 
    If everything runs correctly the script will output something like this. 
 
-   ![](psong_images/deploy_output.png)
+   ![](images/deploy-output.png)
 
 
 2. Check the status using the following commands
 
 The following command returns the Kubernetes service of MyToDo application with a load balancer exposed through an external API
   ```
+  <copy>
   services
+  </copy>
   ```
   This will run `kubectl get services` in the background, but the setup script creates aliases for ease of use
 
-![](psong_images/get_services.png)
+![](images/get-services.png)
 
 3. The following command returns all the pods running in your kubernetes cluster:
   ```
+  <copy>
   pods
+  </copy>
   ```
 This will run `kubectl get pods` in the background, but the setup script creates aliases for ease of use
 
-![](psong_images/get_pods.png)
+![](images/get-pods.png)
 
 5. You can tail the log of one of the pods by running:
 
   ```
+  <copy>
   kubectl -n mtdrworkshop logs -f <pod name>
+  </copy>
   ```
 
   $ kubectl logs -f <pod name>
   Example: `kubectl -n mtdrworkshop logs -f todolistapp-helidon-se-deployment-7fd6dcb778-c9dbv`
 
-![](psong_images/pod_logs.png)
+![](images/pod-logs.png)
 
   If the logs return `webserver is up!` then you have done everything correctly.
-## **Task 3**: UnDeploy (optional)
+## Task 3: UnDeploy (optional)
 
   If you make changes to the image, you need to delete the service and the pods by running undeploy.sh then redo Steps 2 & 3.
 
   1. Run the `undeploy.sh` script
   ```
-    cd $MTDRWORKSHOP_LOCATION/backend; ./undeploy.sh
+  <copy>
+  cd $MTDRWORKSHOP_LOCATION/backend
+  ./undeploy.sh
+  </copy>
   ```
   2. Rebuild the image + Deploy + (Re)Configure the API Gateway
 
-## **Task 4**: Configure the API Gateway
+## Task 4: Configure the API Gateway
 
 The API Gateway protects any RESTful service running on Container Engine for Kubernetes, Compute, or other endpoints through policy enforcement, metrics and logging.
 Rather than exposing the Helidon service directly, we will use the API Gateway to define cross-origin resource sharing (CORS).
 
 The setup script already creates an API gateway, but you still need to create the deployments in the API gateway.
 
 1. From the hamburger  menu navigate **Developer Services** > **API Management > Gateways**
-   ![](psong_images/api_gateway_navigate.png)
+   ![](images/api-gateway-navigate.png)
 
 2. Click on the todolist gateway that has been created for you
-   ![](psong_images/select_gateway.png)
+   ![](images/select-gateway.png)
 
 3. Create a todolist deployment by clicking create deployment
-   ![](psong_images/create_deployment.png)
+   ![](images/create-deployment.png)
 
 4. Fill out the basic information like so:
 
-![](psong_images/basic_information_deployment.png)
+![](images/basic-information-deployment.png)
 5. Configure Cross-origin resource sharing (CORS) policies.
   - CORS is a security mechanism that will prevent loading resources from unspecified origins (domain, scheme, or port).
   - Allowed Origins: is the list of all servers (origins) that are allowed to access the API deployment typically your Kubernetes cluster IP.
@@ -148,35 +166,35 @@ The setup script already creates an API gateway, but you still need to create th
 
   To configure CORS, scroll down and click add next to CORS and fill in this information under allowed origins. These are the origins that can load resources to your application.
 
-  ![](psong_images/cors_information.png)
+  ![](images/cors-information.png)
 
 6. Configure the Headers
 
-    ![](images/Headers.png)
+    ![](images/headers.png)
 
 7. Configure the routes: we will define two routes:
   - /todolist for the first two APIs: GET, POST and OPTIONS
 
-  ![](psong_images/route_1.png)
+  ![](images/route-1.png)
 
 - /todolist/{id} for the remaining three APIs: (GET, PUT and DELETE)
 
-![](psong_images/route_2.png)
+![](images/route-2.png)
 
 
-## **Task 5**: Testing the backend application through the API Gateway
+## Task 5: Testing the Backend Application Through the API Gateway
 
 1. Navigate to the newly create Gateway Deployment Detail an copy the endpoint
-   ![](psong_images/copy_endpoint.png " ")
+   ![](images/copy-endpoint.png " ")
 
 2. Testing through the API Gateway endpoint
   postfix the gateway endpoint with "/todolist" as shown in the image below
 
-   ![](psong_images/endpoint_successful.png " ")
+   ![](images/endpoint-successful.png " ")
 
   It should display the Todo Item(s) in the TodoItem table that was created during the setup.
 
-Congratulations, you have completed lab 2; you may now [proceed to the next lab](#next).
+You may now **proceed to the next lab**.
 
 ## Acknowledgements