summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: e61ad57)
raw | patch | inline | side by side (parent: e61ad57)
author | Christoph Saalfeld <saalfeld@amazon.com> | |
Thu, 8 Oct 2015 01:43:38 +0000 (18:43 -0700) | ||
committer | Christoph Saalfeld <saalfeld@amazon.com> | |
Thu, 8 Oct 2015 01:43:38 +0000 (18:43 -0700) |
PortingGuide.md | patch | blob | history |
diff --git a/PortingGuide.md b/PortingGuide.md
index e234a66c15f20126e1765115af73660eddfc66d3..d6cb633b0c3992902f6b5b21092941aaae40f288 100755 (executable)
--- a/PortingGuide.md
+++ b/PortingGuide.md
\r
`certs` : This directory is initially empty and will need to contain the private key, the client certificate and the root CA. The client certificate and private key can be downloaded from the AWS IoT console or be created using the AWS CLI commands. The root CA can be downloaded from [here](https://www.symantec.com/content/en/us/enterprise/verisign/roots/VeriSign-Class%203-Public-Primary-Certification-Authority-G5.pem)\r
\r
-`docs` : SDK API and file documentation.\r
+`docs` : [Device SDK API and file documentation](http://aws-iot-device-sdk-embedded-c-docs.s3-website-us-east-1.amazonaws.com/index.html).\r
\r
`mbedtls_lib` : The mbedTLS source files. This directory is included when downloading the mbedTLS version of the SDK. It contains the mbedTLS source files to be built into the device application.\r
\r