updated image lines in content

Signed-off-by: dishanktiwari2501 <[email protected]>

content/sass/opsworks_migration.md

@@ -32,15 +32,15 @@ The steps to migrate from  AWS OPSWorks to Chef SaaS is given below:
 
 1. You will get a SaaS environment to start the process. The image is given below:
 
-  IMAGE
+    IMAGE
 
 1. Once the environment is created, the environment will be inserted under the monitoring tools.
 
-  IMAGE
+    IMAGE
 
 1. As a part of the process, a deployment will take place in a Blue/Green method which will directly link to your public DNS.
 
-  IMAGE
+    IMAGE
 
 1. Once the environment is created, you will get:
 
@@ -52,19 +52,19 @@ The steps to migrate from  AWS OPSWorks to Chef SaaS is given below:
 
 1. Once you receive the generic information that the SaaS environment is ready it is time to make a backup of the OPSWorks environment.
 
-  IMAGE
+    IMAGE
 
 1. Download the backup in **.zip** format, once it is created.
 
-  IMAGE
+    IMAGE
 
 1. While created a SaaS environment, a S3 bucket has also been created that can be used for storing the backup. The S3 bucket expires in 14 days after the environment set up and will only allow once backup file per bucket. If you provide two or more files, only the last upload will remain in the bucket.
 
-  IMAGE
+    IMAGE
 
 1. Once the above steps are done, a backup will be restores into your new SaaS environment.
 
-  IMAGE
+    IMAGE
 
 1. Once the restoring is done, you can login to Chef SaaS using your OPSWorks credentials. After logging in, you will see data in the environment up to the day of the backup. This will include users, cookbooks, client runs, ECT.