From 04fe7b07f675a62422273bf1e99e26e0626f55b4 Mon Sep 17 00:00:00 2001 From: Kody Stribrny Date: Tue, 12 Sep 2023 14:34:05 -0700 Subject: [PATCH] Merge readme update to one line for consistency --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index d8c02d62b9..d29f23ab5d 100755 --- a/README.md +++ b/README.md @@ -410,8 +410,7 @@ In order to set these configurations manually, edit `demo_config.h` in `demos/mq * Set `CLIENT_CERT_PATH` to the path of the client certificate downloaded when setting up the device certificate in [AWS IoT Account Setup](#aws-iot-account-setup). * Set `CLIENT_PRIVATE_KEY_PATH` to the path of the private key downloaded when setting up the device certificate in [AWS IoT Account Setup](#aws-iot-account-setup). -It is possible to configure `ROOT_CA_CERT_PATH` to any PEM-encoded Root CA Certificate. However, this is optional because CMake will download and set it to [AmazonRootCA1.pem](https://www.amazontrust.com/repository/AmazonRootCA1.pem) when unspecified. If unspecified, the default Root CA -path will be interpreted relative to where the demo binary is executed. For many demos, you can change this path by modifying it in the corresponding `demo_config.h`. +It is possible to configure `ROOT_CA_CERT_PATH` to any PEM-encoded Root CA Certificate. However, this is optional because CMake will download and set it to [AmazonRootCA1.pem](https://www.amazontrust.com/repository/AmazonRootCA1.pem) when unspecified. If unspecified, the default Root CA path will be interpreted relative to where the demo binary is executed. For many demos, you can change this path by modifying it in the corresponding `demo_config.h`. #### Configuring AWS IoT Device Defender and AWS IoT Device Shadow demos