Skip to content

Commit 4f916d1

Browse files
Juan Flores MuñozFranFin
andauthored
Update _docs/tutorials/advanced/nuttx/tcp_echo/index.md
Co-Authored-By: FranFin <58737168+FranFin@users.noreply.github.com>
1 parent e4e4f86 commit 4f916d1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • _docs/tutorials/advanced/nuttx/tcp_echo

_docs/tutorials/advanced/nuttx/tcp_echo/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ permalink: /docs/tutorials/advanced/nuttx/tcp_echo/
77
|:-----:|:-----------------:|
88
| NuttX | Olimex-STM32-E407 |
99

10-
On this tutorial, we will see how to use a TCP echo server on NuttX, to test a basic TCP server.TCP (Transmission Control Protocol) is connection-oriented protocol, and a connection between client and server is established (passive open) before data can be sent.
10+
In this tutorial, we will see how to use a TCP echo server on NuttX, to test a basic TCP server. TCP (Transmission Control Protocol) is a connection-oriented protocol, and a connection between client and server is established (passive open) before data can be sent.
1111

1212
## Hardware requirements:
1313
- [Olimex-STM32-E407 board](https://www.olimex.com/Products/ARM/ST/STM32-E407/open-source-hardware)
@@ -149,4 +149,4 @@ netcat 192.168.1.130 80
149149
hello micro-ROS!
150150
hello micro-ROS!
151151
```
152-
When you write something on the TCP client, if everything goes fine, it should receive the same message that you send.
152+
When you write something on the TCP client, if everything goes fine, it should receive the same message that you send.

0 commit comments

Comments
 (0)