From cf0e0780ce14393c3bfc5b90f4dd1862a5335621 Mon Sep 17 00:00:00 2001 From: Yang Hau Date: Thu, 11 Jul 2024 00:47:56 +0800 Subject: [PATCH] fix the typos --- rtos-docs/netx-duo/chapter3.md | 4 ++-- rtos-docs/netx-duo/chapter4.md | 2 +- rtos-docs/netx-duo/chapter5.md | 12 ++++++------ rtos-docs/netx-duo/netx-duo-bsd/chapter2.md | 4 ++-- rtos-docs/netx-duo/netx-duo-nat/chapter2.md | 2 +- rtos-docs/netx-duo/netx-duo-smtp-client/chapter2.md | 2 +- 6 files changed, 13 insertions(+), 13 deletions(-) diff --git a/rtos-docs/netx-duo/chapter3.md b/rtos-docs/netx-duo/chapter3.md index 8e452b4..ec87c76 100644 --- a/rtos-docs/netx-duo/chapter3.md +++ b/rtos-docs/netx-duo/chapter3.md @@ -1526,7 +1526,7 @@ In gPTP module of NetxDuo, following functionalities are provided: SRP (Stream Reservation Protocol) is a protocol used in Time-Sensitive Networking (TSN). It allows devices to reserve resources for specific streams of data across the network. This ensures that these streams have the necessary bandwidth and can meet their time sensitivity requirements. In SRP module of NetxDuo, following functionalities are provided: -- Initializaiton of SRP service. +- Initialization of SRP service. - Starting and stopping the SRP talker service. - Starting and stopping the SRP listener service. @@ -1558,5 +1558,5 @@ In MRP module of NetxDuo, following functionalities are provided to MRP applicat - Provide the interface of MRP initialization. - Maintaining state machine for MRP applications. - Process the event triggered by receiving different MRP messages. -- Receiveing the message from ethernet, and destribute the MRP messages to the corresponding MRP applications. +- Receiving the message from ethernet, and distribute the MRP messages to the corresponding MRP applications. - Handle the timer event for MRP applications. diff --git a/rtos-docs/netx-duo/chapter4.md b/rtos-docs/netx-duo/chapter4.md index bf95ccc..abd7953 100644 --- a/rtos-docs/netx-duo/chapter4.md +++ b/rtos-docs/netx-duo/chapter4.md @@ -13205,7 +13205,7 @@ UINT nx_srp_talker_start(NX_SRP *srp_ptr, NX_MSRP_DOMAIN *srp_domain, UCHAR *str ``` ### Description -This function start SRP talker, it sets event callback funtions and register domain, Vlan, stream request. +This function start SRP talker, it sets event callback functions and register domain, Vlan, stream request. ### Parameters diff --git a/rtos-docs/netx-duo/chapter5.md b/rtos-docs/netx-duo/chapter5.md index f378e42..99f28b5 100644 --- a/rtos-docs/netx-duo/chapter5.md +++ b/rtos-docs/netx-duo/chapter5.md @@ -83,7 +83,7 @@ The following NX_IP_DRIVER members are used for the disable link request. | nx_ip_driver_status | Completion status. If the driver is not able to disable the specified interface in the IP instance, it will return a non-zero error status. | ### Uninitialize Link -This request is made by NetX Duo during the deletion of an IP instance by the ***nx_ip_delete*** service. This request uninitialize the interface, and release any resources created during initialization phase. Typically it is a reverse operation of the ***Initialize Link*** operation. After the interface is uninitalized, the device cannot be used until the interface is initialized again. +This request is made by NetX Duo during the deletion of an IP instance by the ***nx_ip_delete*** service. This request uninitialized the interface, and release any resources created during initialization phase. Typically it is a reverse operation of the ***Initialize Link*** operation. After the interface is uninitialized, the device cannot be used until the interface is initialized again. The following NX_IP_DRIVER members are used for the disable link request. @@ -567,7 +567,7 @@ the driver entry: UINT nx_driver_shaper_cbs_entry(NX_SHAPER_DRIVER_PARAMETER *parameter) ``` -Data structure of driver entry paramter: +Data structure of driver entry parameter: ```C typedef struct NX_SHAPER_DRIVER_PARAMETER_STRUCT { @@ -594,7 +594,7 @@ the driver entry parameter: | parameter -> nx_shaper_driver_command | Description | | ------------------------------------------- | -----------------------------------------------------------------| | ***NX_SHAPER_COMMAND_INIT*** | initialization of enabling CBS, | -| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capablity of CBS, | +| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capability of CBS, | | ***NX_SHAPER_COMMAND_PARAMETER_SET*** | set parameter passed from application to driver, | @@ -627,7 +627,7 @@ the driver entry parameter: | parameter -> nx_shaper_driver_command | Description | | ------------------------------------------- | -----------------------------------------------------------------| | ***NX_SHAPER_COMMAND_INIT*** | initialization of enabling TAS, | -| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capablity of TAS, | +| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capability of TAS, | | ***NX_SHAPER_COMMAND_PARAMETER_SET*** | set parameter passed from application to driver, | ### Frame preemption (FPE) - 802.1Qbu @@ -640,7 +640,7 @@ UINT nx_driver_shaper_fpe_entry(NX_SHAPER_DRIVER_PARAMETER *parameter) ``` -Data stucture of TAS parameter which define the necessary parameters that TAS driver needs. +Data structure of TAS parameter which define the necessary parameters that TAS driver needs. ```C typedef struct NX_SHAPER_FP_PARAMETER_STRUCT { @@ -657,5 +657,5 @@ the driver entry parameter: | parameter -> nx_shaper_driver_command | Description | | ------------------------------------------- | -----------------------------------------------------------------| | ***NX_SHAPER_COMMAND_INIT*** | initialization of enabling FPE, | -| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capablity of FPE, | +| ***NX_SHAPER_COMMAND_CONFIG*** | set hardware queue priority and capability of FPE, | | ***NX_SHAPER_COMMAND_PARAMETER_SET*** | set parameter passed from application to driver, | \ No newline at end of file diff --git a/rtos-docs/netx-duo/netx-duo-bsd/chapter2.md b/rtos-docs/netx-duo/netx-duo-bsd/chapter2.md index e5397df..fd6137e 100644 --- a/rtos-docs/netx-duo/netx-duo-bsd/chapter2.md +++ b/rtos-docs/netx-duo/netx-duo-bsd/chapter2.md @@ -416,7 +416,7 @@ UINT status; printf("Error in Enable TCP \n"); } - /* Now initialize BSD Scoket Wrapper */ + /* Now initialize BSD Socket Wrapper */ status = bsd_initialize (&bsd_ip, &bsd_pool,pointer, 2048, 2); } @@ -870,7 +870,7 @@ UINT status; printf("Error in Enable TCP \n"); } - /* Now initialize BSD Scoket Wrapper */ + /* Now initialize BSD Socket Wrapper */ status = bsd_initialize(&bsd_ip, &bsd_pool,pointer, 2048, 2); /* Check BSD initialize status. */ diff --git a/rtos-docs/netx-duo/netx-duo-nat/chapter2.md b/rtos-docs/netx-duo/netx-duo-nat/chapter2.md index 519eb4f..3f1eb69 100644 --- a/rtos-docs/netx-duo/netx-duo-nat/chapter2.md +++ b/rtos-docs/netx-duo/netx-duo-nat/chapter2.md @@ -385,7 +385,7 @@ NX_PACKET *my_packet; } #endif - /* External Host ping NAT External address, NAT IP instance will response the requet. */ + /* External Host ping NAT External address, NAT IP instance will response the request. */ status = nx_icmp_ping(&external_ip, NX_NAT_EXTERNAL_IPADR, "ABCDEFGHIJKLMNOPQRSTUVWXYZ", 28, &my_packet, 100); diff --git a/rtos-docs/netx-duo/netx-duo-smtp-client/chapter2.md b/rtos-docs/netx-duo/netx-duo-smtp-client/chapter2.md index 3236348..25b5129 100644 --- a/rtos-docs/netx-duo/netx-duo-smtp-client/chapter2.md +++ b/rtos-docs/netx-duo/netx-duo-smtp-client/chapter2.md @@ -110,7 +110,7 @@ void tx_application_define(void *first_unused_memory) /* Create SMTP Client packet pool. This is only for transmitting packets to the server. It need not be a separate packet pool than the IP default packet pool but for more efficient resource use, we use two different packet pools - because the CLient SMTP messages generally require more payload than IP + because the Client SMTP messages generally require more payload than IP control packets. Packet payload depends on the SMTP Client application requirements. Size of