Rectify instruction writing style

Author: DakshitBabbar

README.md

@@ -505,19 +505,21 @@ The following creates a job that specifies a Linux Kernel link for downloading.
         --targets arn:aws:iot:us-west-2:<account-id>:thing/<thing-name> \
         --document '{"url":"https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.8.5.tar.xz"}'
 ```
-3. After this we need to run the demo using the command:
+3. Execute the following command:
 ```
 /build/bin/jobs_demo_mosquitto
 ```
-the above command will give all he instructions on how to run the demo. It will ask you to run the following command to run the demo:
+This command will provide detailed instructions for running the demo.
 
-```
+4. When prompted, run the demo using this command:
+```    
 ./build/bin/jobs_demo_mosquitto \
 -n <thing-name> \
 -h <aws-iot endpoint> \
 --certfile <device certificate of the thing> \
 --keyfile <private key of the thing>
-```
+``` 
+Note: Replace the placeholders in angle brackets with your specific information.
 
 
 #### Setup for the Greengrass local auth demo
@@ -643,7 +645,7 @@ Any version after 1.6.14 will drop privileges as soon as the configuration file
     openssl req -x509 -nodes -sha256 -days 365 -newkey rsa:2048 -keyout ca.key -out ca.crt
     ```
 
-    When asked for the Common Name (CN) after running the following command enter the same value as was added for the macro `BROKER_ENDPOINT` in the demo_config.h file, which in our case is just `localhost`
+    You will be prompted to configure the Common Name (CN) after running the following command. It's crucial to enter the same value that was specified for the `BROKER_ENDPOINT` macro in the demo_config.h file. In this particular instance, the correct value to enter is simply "localhost".
     ```sh
     # Generate server key and certificate.# Provide the Subject field information as appropriate for Server certificate. Make sure the Common Name (CN) field is different from the root CA certificate.
     openssl req -nodes -sha256 -new -keyout server.key -out server.csr # Sign with the CA cert.
@@ -683,18 +685,30 @@ Run httpbin through port 80:
 docker pull kennethreitz/httpbin
 docker run -p 80:80 kennethreitz/httpbin
 ```
+The `kennetheitz/httpbin` docker image is not compatible with linux/arm64 platform that is used by Mac machines. Hence instead of that use `mccutchen/go-httpbin`.
+```sh
+#To install the image run:
+
+$ docker pull mccutchen/go-httpbin
+
+#To run the server on local host on port 80 run
+
+$ docker run -p 80:8080 mccutchen/go-httpbin
+```
+
 
 `SERVER_HOST` defined in `demos/http/http_demo_plaintext/demo_config.h` can now be set to `localhost`.
 
 To run `http_demo_basic_tls`, you could use either [Tunnelmole](https://github.com/robbie-cahill/tunnelmole-client), an open source tunneling tool, or [ngrok](https://ngrok.com/download), a popular closed source tunneling tool, to create an HTTPS tunnel to the httpbin server currently hosted on port 80:
 
 **Using Tunnelmole**
+
 First, install Tunnelmole. On Linux, Mac and Windows Subsystem for Linux, use
 
 ```sh
 curl -O https://tunnelmole.com/sh/install.sh && sudo bash install.sh
 ```
-
+The above may not function correctly on ARM machines like mac. As an alternative, you can clone the repository and build the application from its source code. 
 For Windows without WSL, [download tmole.exe](https://tunnelmole.com/downloads/tmole.exe) and add it to your [PATH](https://www.wikihow.com/Change-the-PATH-Environment-Variable-on-Windows).
 
 Then run `tmole 80`
@@ -717,7 +731,17 @@ Set `SERVER_HOST` in `demos/http/http_demo_basic_tls/demo_config.h` to the https
 
 Set `SERVER_HOST` in `demos/http/http_demo_basic_tls/demo_config.h` to the https link provided by ngrok, without `https://` preceding it.
 
-You must also download the Root CA certificate provided by the ngrok https link and set `ROOT_CA_CERT_PATH` in `demos/http/http_demo_basic_tls/demo_config.h` to the file path of the downloaded certificate.
+**Getting the Root CA**
+
+Download the Root CA certificate from the obtained https link. To obtain this:
+
+1. Open the https link in your browser.
+2. Click on the https lock button in the url bar.
+3. Download the chain of certificates.
+4. Locate the last certificate in the chain - this is your required Root CA certificate.
+5. Copy this certificate and paste it into a new .pem file.
+
+Set the macro ROOT_CA_CERT_PATH in demo_config.h to the file path of your newly created Root CA certificate.
 
 ## Generating Documentation
 Note: For pre-generated documentation, please visit [Releases and Documentation](#releases-and-documentation) section.

demos/fleet_provisioning/readme.md

@@ -1,39 +1,39 @@
 ## Setup for Fleet Provisioning Demos
 
-### Creating the Provisioning Policy
-
-1. Login to your AWS account and open AWS IoT Core. On the side bar click on security > policies > create policy
-2. Set a relevant policy name
-3. Copy the contents in the demos/fleet_provisioning/fleet_provisioning_with_csr(or fleet_provisioning_keys_cert_demo)/example_claim_policy.json and paste it in the policy document on the AWS console.
-4. Create the policy
-
-
-### Creating the Claim Certificate
-
-1. On the side bar of the AWS IoT Core click on security > certificates > add certificate. Make the “Certificate Status” active and download the certificate files from the prompt given.
-2. Set the value of the macro CLAIM_CERT_PATH in the democonfig.h file to the path of the certificate downloaded and set the value of the macro CLAIM_PRIVATE_KEY_PATH in the democonfig.h file to the path of the private key downloaded. Alternatively you can set the values of these through command line parameters.
-3. Now click on the certificate > attach policies > select your provisioning policy made in the previous section and select attach policy.
-
-
-### Creating the IAM role for AWS IoT to create resources
-
-1. Go to the IAM Identity center and create a new IAM role
-2. Select AWS IoT when asked to select a service
-
-
-### Creating Fleet Provisioning Template
-
-1. Go to AWS IoT Core > Connect many devices > Connect many devices > create provisioning template.
-2. Select Provisioning devices with claim certificates > next
-3. Set the status to active
-4. Enter template name
-5. Enter the IAM role you created in the previous section or you can create a new one if you have not yet created it
-6. Enter the provisioning policy that you made in the very first section or create a new one if you havn’t already
-7. We do not need to do any pre-provisioning stuff hence we will select “Don’t use a pre-provisioning action”
-8. Turn the automatic thing creation option on and click next
-9. Select a policy that you wish your device should have when it is running (Permissions to connet to IoT, subscribe to some topic, publish to some topic extra) or make a new one if you do not have one already.
-10. Click next, review and create.
-
-### Configuring the demo
-Set all the necessary macro values in the demo_config.h file or alternatively you can set the values of these through command line parameters.
-
+### Create the Provisioning Policy
+
+1. Log in to your AWS account and open AWS IoT Core.
+2. Navigate to Security > Policies > Create policy.
+3. Enter a relevant policy name.
+4. Copy the contents from demos/fleet_provisioning/fleet_provisioning_with_csr (or fleet_provisioning_keys_cert_demo)/example_claim_policy.json.
+5. Paste the copied content into the policy document on the AWS console.
+6. Click "Create policy".
+
+### Create the Claim Certificate
+1. In AWS IoT Core, go to Security > Certificates > Add certificate.
+2. Set the "Certificate Status" to active.
+3. Download the certificate files from the provided prompt.
+4. Update the demo_config.h file:
+    - Set CLAIM_CERT_PATH to the path of the downloaded certificate.
+    - Set CLAIM_PRIVATE_KEY_PATH to the path of the downloaded private key. Note: You can also set these values using command line parameters.
+5. Select the certificate, click "Attach policies", choose your provisioning policy, and click "Attach policy".
+
+### Create the IAM Role for AWS IoT
+1. Go to the IAM Identity Center.
+2. Create a new IAM role.
+3. When prompted, select AWS IoT as the service.
+
+### Create Fleet Provisioning Template
+1. Navigate to AWS IoT Core > Connect many devices > Connect many devices > Create provisioning template.
+2. Choose "Provisioning devices with claim certificates" and click "Next".
+3. Set the status to active.
+4. Enter a template name.
+5. Select the IAM role you created earlier (or create a new one if needed).
+6. Choose the provisioning policy you created earlier (or create a new one if needed).
+7. Select "Don't use a pre-provisioning action".
+8. Enable the automatic thing creation option and click "Next".
+9. Select or create a policy for your device's permissions (e.g., connecting to IoT, subscribing/publishing to topics).
+10. Click "Next", review the settings, and create the template.
+
+### Configure the Demo
+Set all necessary macro values in the demo_config.h file. Alternatively, you can provide these values through command line parameters.

demos/greengrass/greengrass_demo_local_auth/README.md

@@ -93,7 +93,7 @@ openssl x509 -req \
 
 8. Create a new thing and link it with this new certificate thing_cert.pem and set the value of the macro `THING_NAME` in demo_config.h file to the name of this new thing
 
-9. Set the value of the macro `CLIENT_CERT_PATH` to the path of  thing_cert.pem and the value of the macro `CLIENT_PRIVATE_KEY_PATH` thing_private.key
+9. Set the value of the macro `CLIENT_CERT_PATH` to the path of thing_cert.pem and the value of the macro `CLIENT_PRIVATE_KEY_PATH` to the path of thing_private.key
 
 ### Configuring the GG core for local auth and MQTT
 
@@ -105,7 +105,7 @@ Deploy the following components to your Greengrass core:
 
 Set the configuration for the aws.greengrass.clientdevices.Auth component based
 off the [provided config](./greengrass_auth_conf.json). Ensure the certificate
-paths match the files created for your custom CA above and their absolute paths are written after `file://`
+paths match the files created for your custom CA above and their absolute paths are written after `file://`.
 
 This config will allow associated Things to publish and subscribe to any topic
 on the Greengrass core broker.