Diff: README.md

Revision:

32:5fa61ebc2689

Parent:

30:4825e4f38844

Child:

33:2efadc4d8784

--- a/README.md	Tue Mar 27 11:57:33 2018 +0200
+++ b/README.md	Tue Oct 30 11:07:46 2018 +0800
@@ -1,6 +1,6 @@
-# mbed-os-example-http(s)
+# HTTP/HTTPS example for Mbed OS 5
 
-This application demonstrates how to make HTTP and HTTPS requests and parse the response from mbed OS 5.
+This application demonstrates how to make HTTP and HTTPS requests and parse the response from Mbed OS 5.
 
 It consists of six demo's, which you can select in ``source/select-demo.h``.
 
@@ -8,7 +8,7 @@
     * Does a GET request to http://httpbin.org/status/418.
     * Does a POST request to http://httpbin.org/post.
 * HTTPS demo:
-    * Does a GET request to https://developer.mbed.org/media/uploads/mbed_official/hello.txt.
+    * Does a GET request to https://os.mbed.com/media/uploads/mbed_official/hello.txt.
     * Does a POST request to https://httpbin.org/post.
 * HTTP demo with socket re-use.
 * HTTPS demo with socket re-use.
@@ -21,18 +21,24 @@
 
 ## To build
 
-1. Open ``mbed_app.json`` and change the `network-interface` option to your connectivity method ([more info](https://github.com/ARMmbed/easy-connect)).
-2. Build the project in the online compiler or using mbed CLI.
-3. Flash the project to your development board.
-4. Attach a serial monitor to your board to see the debug messages.
+1. If you're using WiFi, specify the credentials in `mbed_app.json`.
+1. Build the project in the online compiler or using Mbed CLI.
+1. Flash the project to your development board.
+1. Attach a serial monitor to your board to see the debug messages.
+
+## Defining the network interface
+
+This application uses the on-board network interface for your board. If you use an external network interface (f.e. a WiFi module) you need to add the driver to this project. Then, open `network-helper.h` and specify which network driver to use.
+
+More information is in the Mbed OS documentation under [IP Networking](https://os.mbed.com/docs/latest/reference/ip-networking.html).
 
 ## Entropy (or lack thereof)
 
-On all platforms **except** the FRDM-K64F, FRDM-K22F and EVK-ODIN-W2, the application is compiled without TLS entropy sources. This means that your code is inherently unsafe and should not be deployed to any production systems. To enable entropy, remove the `MBEDTLS_NO_DEFAULT_ENTROPY_SOURCES` and `MBEDTLS_TEST_NULL_ENTROPY` macros from mbed_app.json.
+On all platforms that do not have the `TRNG` feature, the application is compiled without TLS entropy sources. This means that your code is inherently unsafe and should not be deployed to any production systems. To enable entropy, remove the `MBEDTLS_NO_DEFAULT_ENTROPY_SOURCES` and `MBEDTLS_TEST_NULL_ENTROPY` macros from mbed_app.json.
 
 ## Flash size
 
-Default flash size for HTTPS is very large, as the application is loading the default mbed TLS configuration. To use a more optimized version, include `mbedtls_config.h` in your mbed_app.json, by adding:
+Default flash size for HTTPS is very large, as the application is loading the default Mbed TLS configuration. To use a more optimized version, you can disable unused cypher suites and other Mbed TLS features with a custom configuration file. Create a new configuration file, then add in `mbed_app.json`:
 
 ```
 "MBEDTLS_CONFIG_FILE=\"mbedtls_config.h\""