mirror/lwip
1
0
Fork 0
mirror of https://github.com/lwip-tcpip/lwip.git synced 2024-12-25 00:14:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos in docs

Browse Source
This commit is contained in:
Dirk Ziegelmeier 2016-08-08 12:15:58 +02:00
parent 282b8a2b6c
commit fa568f7750
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README
View File

@ -77,7 +77,7 @@ Self documentation of the source code is regularly extracted from the current
Git sources and is available from this web page: Git sources and is available from this web page:
http://www.nongnu.org/lwip/ http://www.nongnu.org/lwip/
There is now a constantly growin wiki about lwIP at There is now a constantly growing wiki about lwIP at
http://lwip.wikia.com/wiki/LwIP_Wiki http://lwip.wikia.com/wiki/LwIP_Wiki
Also, there are mailing lists you can subscribe at Also, there are mailing lists you can subscribe at

2
UPGRADING
View File

@ -78,7 +78,7 @@ with newer versions.
* support PBUF_REF for RX packets * support PBUF_REF for RX packets
* LWIP_NETCONN_FULLDUPLEX allows netconn/sockets to be used for reading/writing from separate * LWIP_NETCONN_FULLDUPLEX allows netconn/sockets to be used for reading/writing from separate
threads each (needs LWIP_NETCONN_SEM_PER_THREAD) threads each (needs LWIP_NETCONN_SEM_PER_THREAD)
* Moved and reorderd stats (mainly memp/mib2) * Moved and reordered stats (mainly memp/mib2)
(1.4.0) (1.4.0)

2
doc/contrib.txt
View File

@ -39,7 +39,7 @@ features of Savannah help us not lose users' input.
bugtracker at Savannah. bugtracker at Savannah.
3. If you have a fix put the patch on Savannah. If it is a patch that affects 3. If you have a fix put the patch on Savannah. If it is a patch that affects
both core and arch specific stuff please separate them so that the core can both core and arch specific stuff please separate them so that the core can
be applied separately while leaving the other patch 'open'. The prefered way be applied separately while leaving the other patch 'open'. The preferred way
is to NOT touch archs you can't test and let maintainers take care of them. is to NOT touch archs you can't test and let maintainers take care of them.
This is a good way to see if they are used at all - the same goes for unix This is a good way to see if they are used at all - the same goes for unix
netifs except tapif. netifs except tapif.