Skip to content

Commit d2caaad

Browse files
committed
Apply changes suggested during review to README.md
1 parent 7b828b3 commit d2caaad

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

README.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This application downloads a file from an HTTPS server (developer.mbed.org) and
99
* An Ethernet cable and connection to the internet.
1010

1111
## Required software
12-
* [mbed-cli](https://github.com/ARMmbed/mbed-cli) - to build the example program. To learn how to build mbed OS applications with mbed-cli, see the [user guide](https://github.com/ARMmbed/mbed-cli/blob/master/README.md)
12+
* [mbed CLI](https://github.com/ARMmbed/mbed-cli) - to build the example program. To learn how to build mbed OS applications with mbed CLI, see the [user guide](https://github.com/ARMmbed/mbed-cli/blob/master/README.md)
1313
* [Serial port monitor](https://developer.mbed.org/handbook/SerialPC#host-interface-and-terminal-applications).
1414

1515
## Getting started
@@ -18,9 +18,9 @@ This application downloads a file from an HTTPS server (developer.mbed.org) and
1818

1919
2. Open a command line tool and navigate to the project’s directory.
2020

21-
3. Update mbed-os sources using the `mbed update` command.
21+
3. Update `mbed-os` sources using the `mbed update` command.
2222

23-
4. Build the application by selecting the hardware board and build the toolchain using the command `mbed compile -m K64F -t GCC_ARM -c -j0`. mbed-cli builds a binary file under the project’s `.build` directory.
23+
4. Build the application by selecting the board and build toolchain using the command `mbed compile -m K64F -t GCC_ARM -c -j0`. mbed-cli builds a binary file under the project’s `.build` directory.
2424

2525
5. Connect the FRDM-K64F to the internet using the Ethernet cable.
2626

@@ -40,7 +40,7 @@ The application prints debug messages over the serial port, so you can monitor i
4040
* 8N1.
4141
* No flow control.
4242

43-
After pressing the **RESET** button on the board, the output in the terminal window should look similar to this:
43+
After pressing the **RESET** button on the board, the output in the terminal window should be similar to this:
4444

4545
```
4646
{{timeout;120}}
@@ -110,15 +110,16 @@ To print out more debug information about the TLS connection, edit the file `sou
110110
* Level 4 (the maximum) includes full binary dumps of the packets.
111111

112112

113-
If the TLS connection is failing with an error similar to:
113+
The TLS connection can fail with an error similar to:
114114

115115
```
116116
mbedtls_ssl_write() failed: -0x2700 (-9984): X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
117117
Failed to fetch /media/uploads/mbed_official/hello.txt from developer.mbed.org:443
118118
```
119119

120-
it probably means you need to update the contents of the `SSL_CA_PEM` constant (this can happen if you modify `HTTPS_SERVER_NAME`, or when `developer.mbed.org` switches to a new CA when updating its certificate).
120+
This probably means you need to update the contents of the `SSL_CA_PEM` constant (this can happen if you modify `HTTPS_SERVER_NAME`, or when `developer.mbed.org` switches to a new CA when updating its certificate).
121121

122-
Another reason for this error may be a proxy providing a different certificate. Proxies can be used in some network configurations or for performing man-in-the-middle attacks. If you choose to ignore this error and proceed with the connection anyway, you can change the definition of `UNSAFE` near the top of the file from 0 to 1.
122+
Another possible reason for this error is a proxy providing a different certificate. Proxies can be used in some network configurations or for performing man-in-the-middle attacks. If you choose to ignore this error and proceed with the connection anyway, you can change the definition of `UNSAFE` near the top of the file from 0 to 1.
123+
124+
**Warning:** this removes all security against a possible active attacker, so use at your own risk or for debugging only!
123125

124-
**Warning:** this removes all security against a possible active attacker, therefore use at your own risk, or for debugging only!

0 commit comments

Comments
 (0)