Skip to content

Commit 208ea26

Browse files
committed
typo and grammar in faq
1 parent 6dfd49b commit 208ea26

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

documents/FAQ.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,14 @@ To enable logging in the samples, you will need to set the following system prop
2929
```
3030

3131
* `aws.crt.debugnative`: Whether to debug native (C/C++) code. Can be either `true` or `false`.
32-
* `aws.crt.log.destination`: Where the logs are outputted to. Can be `File`, `Stdout` or `Stderr`. Defaults to `Stderr`.
32+
* `aws.crt.log.destination`: Where the logs are output to. Can be `File`, `Stdout`, or `Stderr`. Defaults to `Stderr`.
3333
* `aws.crt.log.level`: The level of logging shown. Can be `Trace`, `Debug`, `Info`, `Warn`, `Error`, `Fatal`, or `None`. Defaults to `Warn`.
3434
* `aws.crt.log.filename`: The path to save the log file. Only needed if `aws.crt.log.destination` is set to `File`.
3535

3636
For example, to run `BasicPubSub` with logging you could use the following:
3737

3838
```sh
39-
mvn compile exec:java -pl samples/Mqtt/Mqtt5X509 -Daws.crt.debugnative=true -Daws.crt.log.level=Debug -Daws.crt.log.destionation=Stdout -Dexec.mainClass=pubsub.PubSub -Dexec.args='--endpoint <endpoint> --cert <path to cert> --key <path to key>'
39+
mvn compile exec:java -pl samples/Mqtt/Mqtt5X509 -Daws.crt.debugnative=true -Daws.crt.log.level=Debug -Daws.crt.log.destination=Stdout -Dexec.mainClass=pubsub.PubSub -Dexec.args='--endpoint <endpoint> --cert <path to cert> --key <path to key>'
4040
```
4141

4242
You can also enable [CloudWatch logging](https://docs.aws.amazon.com/iot/latest/developerguide/cloud-watch-logs.html) for IoT which will provide you with additional information that is not available on the client side sdk.
@@ -56,7 +56,7 @@ System.out.println(CRT.awsErrorString(errorCode));
5656

5757
### I keep getting AWS_ERROR_MQTT_UNEXPECTED_HANGUP
5858

59-
This could be many different things but it most likely is a policy issue. Start with using a super permissive IAM policy called AWSIOTFullAccess which looks like this:
59+
This could be many different things, but it is most likely a policy issue. Start by using a super permissive IAM policy called AWSIOTFullAccess which looks like this:
6060

6161
``` json
6262
{

0 commit comments

Comments
 (0)