diff --git a/TEST_APPS/testcases/nfc/README.md b/TEST_APPS/testcases/nfc/README.md index 8e4cf59..6d9082e 100644 --- a/TEST_APPS/testcases/nfc/README.md +++ b/TEST_APPS/testcases/nfc/README.md @@ -1,6 +1,6 @@ # NFC tests. -A CI test suite for NFC component. These tests validate card mbed emulation cases. The key use case is an NFC smart poster supporting comissioning workflow. +A CI test suite for NFC component. These tests validate card mbed emulation cases. The key use case is an NFC smart poster supporting commissioning workflow. The SUT (system under test) is the NFC target. Tests exercise the framework and NDEF transactions when a NFC controller driver is used, or when the stack is configured for an NFC EEPROM chip in the system integration. This project is called CreamScone, which is an ice tea framework based cli-driven python test. @@ -42,7 +42,7 @@ ![Basic Overview](img/simple-overview.png) -Because the comissioning workflow application quality is the end goal, the NFC suite includes learnings to design the CI setup needed for future system testing that bring a mobile phone into the test-rig. The use of a mobile and bluetooth pairing as well as the continous integration system is not included. +Because the commissioning workflow application quality is the end goal, the NFC suite includes learnings to design the CI setup needed for future system testing that bring a mobile phone into the test-rig. The use of a mobile and bluetooth pairing as well as the continuous integration system is not included. @@ -288,7 +288,7 @@ } ``` 1. You will want to replace this and reference the desired controller driver. Likewise, this code is where pinout changes have to be made if using the supplied Controller driver. -2. Search for occurences of guard macros `#ifdef TARGET_PN512` , and `#endif`. Add a new guard macro and code for your specific controller driver at the same point. +2. Search for occurrences of guard macros `#ifdef TARGET_PN512` , and `#endif`. Add a new guard macro and code for your specific controller driver at the same point. Note: If the target uses an EEPROM, it need not be powered/running, to be read, mbedOS is not running at that point. @@ -333,4 +333,4 @@ 1. Test test_nfce2e_discovery_loop fails on NFC controller. The NFC controller driver discovery loop cannot be stopped manually. No major functionality is lost, it only prevents a complete disable of NFC at runtime. A bug ticket #IOTPAN-313 was logged to fix the stop function. The Controller still restarts discovery loop normally under app control after a peer disconnects. -1. The smartposter NDEF record wrapper class `smartposter.h` is also provided as part of the NFC examples. The examples are not needed to compile the test app, but this example class may be usefull to customers. This file may thus move into the NFC component in future. +1. The smartposter NDEF record wrapper class `smartposter.h` is also provided as part of the NFC examples. The examples are not needed to compile the test app, but this example class may be useful to customers. This file may thus move into the NFC component in future. diff --git a/TEST_APPS/testcases/nfc/mobileapi.md b/TEST_APPS/testcases/nfc/mobileapi.md index 9c360ae..46c9e59 100644 --- a/TEST_APPS/testcases/nfc/mobileapi.md +++ b/TEST_APPS/testcases/nfc/mobileapi.md @@ -15,7 +15,7 @@ # Overview -A comparison which analyses NFC use cases on mobile, as background to the test case design/implementation in the comissioning workflow :NFC-Bluetooth-pairing application. +A comparison which analyses NFC use cases on mobile, as background to the test case design/implementation in the commissioning workflow :NFC-Bluetooth-pairing application. - Analyse the [Apple API](https://developer.apple.com/documentation/corenfc) - Analyse the [Android API](https://developer.android.com/guide/topics/connectivity/nfc/advanced-nfc#java) - Python test [pynfc modules](https://nfcpy.readthedocs.io/en/latest/modules/index.html) diff --git a/connectivity/docs/Multihoming - Design document.md b/connectivity/docs/Multihoming - Design document.md index 17c0f3e..1ec8a6b 100644 --- a/connectivity/docs/Multihoming - Design document.md +++ b/connectivity/docs/Multihoming - Design document.md @@ -301,7 +301,7 @@ From LWIP documentation we can read. -**"output"** is called by the IP module when it wants to send a packet on the interface. It firts resolves the hardware address, then sends the packet. For ethernet physical layer, this is usually **etharp_output()**. +**"output"** is called by the IP module when it wants to send a packet on the interface. It first resolves the hardware address, then sends the packet. For ethernet physical layer, this is usually **etharp_output()**. **"linkoutput"** is called by **ethernet_output()** when it wants to send a packet on the interface. This function outputs the pbuf as-is on the link medium. @@ -579,7 +579,7 @@ LWIP selects the proper netif on IP layer using **ip\_route**. -Currently it uses only ip adress as input parameter so choice is based on ip adress only. To extend choice ctiteria also to interface index **ip\_route** must be modified and must take desired **interface\_name** as second argument. +Currently it uses only ip address as input parameter so choice is based on ip address only. To extend choice ctiteria also to interface index **ip\_route** must be modified and must take desired **interface\_name** as second argument. Therefore new member with information about **netif interface\_name** bound to current socket should be placed in the common part of all PCB types. @@ -598,7 +598,7 @@ ## DNS changes -Currently in Nsapi_dns module there is only one array for 5 DNS server adresses. +Currently in Nsapi_dns module there is only one array for 5 DNS server addresses. static nsapi_addr_t dns_servers[DNS_SERVERS_SIZE] = { {NSAPI_IPv4, {8, 8, 8, 8}}, // Google @@ -617,7 +617,7 @@ Add interface name as option to DNS query -To resolve IP adress Netsocket module uses following functions +To resolve IP address Netsocket module uses following functions gethostbyname(const char *name, SocketAddress *address, nsapi_version_t version) nsapi_dns_query(NetworkStack *stack, const char *host, SocketAddress *address, nsapi_version_t version) diff --git a/connectivity/drivers/mbedtls/FEATURE_CRYPTOCELL310/Readme.md b/connectivity/drivers/mbedtls/FEATURE_CRYPTOCELL310/Readme.md index f8145b5..ad8af54 100644 --- a/connectivity/drivers/mbedtls/FEATURE_CRYPTOCELL310/Readme.md +++ b/connectivity/drivers/mbedtls/FEATURE_CRYPTOCELL310/Readme.md @@ -28,7 +28,7 @@ ## Enabling optional alternative drivers -Three additional modules that are not enabled by default have alternative implementation support. This allows backward compatability because these modules don't have full functionality and returns `MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED` for some features. The modules are: +Three additional modules that are not enabled by default have alternative implementation support. This allows backward compatibility because these modules don't have full functionality and returns `MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED` for some features. The modules are: * `AES`, which only supports 128 bit key size, as opposed to previous support for all key sizes. * `CMAC`, which only supports AES 128 bit key size, as opposed to previous support for DES and all key sizes. diff --git a/connectivity/netsocket/tests/TESTS/netsocket/README.md b/connectivity/netsocket/tests/TESTS/netsocket/README.md index 60aed92..6e6574e 100644 --- a/connectivity/netsocket/tests/TESTS/netsocket/README.md +++ b/connectivity/netsocket/tests/TESTS/netsocket/README.md @@ -1372,7 +1372,7 @@ Calculate packet loss rate. The maximum tolerated packet loss rate is 30%. -The number of succesful rounds is higher than 70. +The number of successful rounds is higher than 70. ### UDPSOCKET_ECHOTEST_BURST_NONBLOCK @@ -1411,7 +1411,7 @@ Calculate packet loss rate. The maximum tolerated packet loss rate is 30%. -The number of succesful rounds is higher than 70. +The number of successful rounds is higher than 70. ### TCPSOCKET_ECHOTEST_BURST diff --git a/connectivity/netsocket/tests/TESTS/network/wifi/README.md b/connectivity/netsocket/tests/TESTS/network/wifi/README.md index c699ad8..98fb4be 100644 --- a/connectivity/netsocket/tests/TESTS/network/wifi/README.md +++ b/connectivity/netsocket/tests/TESTS/network/wifi/README.md @@ -140,7 +140,7 @@ **Precondition:** -Test the enviroment is set up as specified in the "Test Environment" chapter. +Test the environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -245,7 +245,7 @@ **Precondition:** -Test enviroment is set up as specified in "Test Environment" chapter. +Test environment is set up as specified in "Test Environment" chapter. **Test steps:** @@ -266,7 +266,7 @@ **Precondition:** -Test enviroment is set up as specified in "Test Environment" chapter. +Test environment is set up as specified in "Test Environment" chapter. **Test steps:** @@ -286,7 +286,7 @@ **Preconditions:** -Test enviroment is set up as specified in the "Test Environment" chapter. +Test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -308,7 +308,7 @@ **Precondition:** -Test enviroment is set up as specified in the "Test Environment" chapter. +Test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -330,7 +330,7 @@ **Precondition:** -Test enviroment is set up as specified in the "Test Environment" chapter. +Test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -350,7 +350,7 @@ **Preconditions:** -1. Test enviroment is set up as specified in the "Test Environment" chapter. +1. Test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -378,7 +378,7 @@ **Preconditions:** -1. Test enviroment is set up as specified in the "Test Environment" chapter. +1. Test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -411,7 +411,7 @@ **Precondition:** -The test enviroment is set up as specified in the "Test Environment" chapter. +The test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -432,7 +432,7 @@ **Precondition:** -The test enviroment is set up as specified in the "Test Environment" chapter. +The test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -453,7 +453,7 @@ **Precondition:** -The test enviroment is set up as specified in the "Test Environment" chapter. +The test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -477,7 +477,7 @@ **Precondition:** -The test enviroment is set up as specified in the "Test Environment" chapter. +The test environment is set up as specified in the "Test Environment" chapter. **Test steps:** @@ -496,7 +496,7 @@ **Preconditions:** -1. The test enviroment is set up as specified in the "Test Environment" chapter. +1. The test environment is set up as specified in the "Test Environment" chapter. 2. The test environment must contain less than 10 Wi-Fi SSID within the listening range of DUT; otherwise, adjust the value used in step 2. **Test steps:** diff --git a/connectivity/nfc/docs/nfc_design.md b/connectivity/nfc/docs/nfc_design.md index 6b55111..e674316 100644 --- a/connectivity/nfc/docs/nfc_design.md +++ b/connectivity/nfc/docs/nfc_design.md @@ -298,7 +298,7 @@ virtual void on_connected(); ``` -This is called when a connection to this endpoint is succesfully established. +This is called when a connection to this endpoint is successfully established. ```cpp virtual void on_disconnected(); diff --git a/docs/design-documents/design_template.md b/docs/design-documents/design_template.md index cc78829..df00cf2 100644 --- a/docs/design-documents/design_template.md +++ b/docs/design-documents/design_template.md @@ -86,7 +86,7 @@ And the function should return mbed_error_status_t value indicating the result of the call as below: MBED_SUCCESS if the call is successful. MBED_ERROR_INVALID_ARGUMENT if input values are invalid.` - MBED_ERROR_CONFIG_UNSUPPORTED if the device doesnt support the requested configuration.` + MBED_ERROR_CONFIG_UNSUPPORTED if the device doesn't support the requested configuration.` **Configuration sequence diagram** diff --git a/drivers/usb/tests/TESTS/usb_device/README.md b/drivers/usb/tests/TESTS/usb_device/README.md index d38e7c7..0e0b147 100644 --- a/drivers/usb/tests/TESTS/usb_device/README.md +++ b/drivers/usb/tests/TESTS/usb_device/README.md @@ -68,7 +68,7 @@ ## Running tests 1. Plug both USB interfaces (*DAPLink* and *USB device*) to your host machine. -1. An addtional macro `USB_DEVICE_TESTS` is needed to be defined when runing tests: +1. An additional macro `USB_DEVICE_TESTS` is needed to be defined when running tests: ``` mbed test -t -m -DUSB_DEVICE_TESTS -n *-tests-usb_device-* ``` diff --git a/platform/FEATURE_EXPERIMENTAL_API/FEATURE_PSA/TARGET_MBED_PSA_SRV/TESTS/compliance_its/psa_its_testlist.md b/platform/FEATURE_EXPERIMENTAL_API/FEATURE_PSA/TARGET_MBED_PSA_SRV/TESTS/compliance_its/psa_its_testlist.md index b466a7e..97cd1f3 100644 --- a/platform/FEATURE_EXPERIMENTAL_API/FEATURE_PSA/TARGET_MBED_PSA_SRV/TESTS/compliance_its/psa_its_testlist.md +++ b/platform/FEATURE_EXPERIMENTAL_API/FEATURE_PSA/TARGET_MBED_PSA_SRV/TESTS/compliance_its/psa_its_testlist.md @@ -5,7 +5,7 @@ Following are the requirements of the Storage Test Suite.
1. Unless described in this document, any behaviour that is defined as IMPLEMENTATION_DEFINED in PSA Storage API document is not verified in this document.
-2. Storage Test Cases use UID value starting from 1 onwards. These UID needs to be free for successfull test execution.
+2. Storage Test Cases use UID value starting from 1 onwards. These UID needs to be free for successful test execution.
3. UID values 1 and 2 are reserved as WRITE_ONCE UID.These UID can't be free from testcase. Make sure these are free.
diff --git a/platform/docs/clocks/clocks.md b/platform/docs/clocks/clocks.md index 2d75683..b3a3eba 100644 --- a/platform/docs/clocks/clocks.md +++ b/platform/docs/clocks/clocks.md @@ -133,7 +133,7 @@ There is also a generic `TickerDataClock` which provides a Chrono Clock wrapper for a `ticker_data *`, so that `TickerDataClock::time_point` can be used to express absolute times for arbitrary clocks. -Note that the `TickerDataClock` is a non-standard Chrono clock, in that its `now` method is non-static. The Chrono type-checking will not detect that `TickerDataClock::time_point`s for different tickers are not interchangable. It is generally preferable to use the dedicated `HighResClock` or `LowPowerClock`, but `TickerDataClock` is used by some generic code, to avoid template bloat from separate code for each Clock. +Note that the `TickerDataClock` is a non-standard Chrono clock, in that its `now` method is non-static. The Chrono type-checking will not detect that `TickerDataClock::time_point`s for different tickers are not interchangeable. It is generally preferable to use the dedicated `HighResClock` or `LowPowerClock`, but `TickerDataClock` is used by some generic code, to avoid template bloat from separate code for each Clock. The base classes `TimerBase`, `TickerBase` and `TimeoutBase` use `TickerDataClock` to provide the core of the high-level implementation, and these are then used to provide the separate strongly-typed high-resolution and low-power classes above. diff --git a/platform/docs/crash-reporting/crash_reporting.md b/platform/docs/crash-reporting/crash_reporting.md index be89a13..5e9ae1d 100644 --- a/platform/docs/crash-reporting/crash_reporting.md +++ b/platform/docs/crash-reporting/crash_reporting.md @@ -99,7 +99,7 @@ ... //Below are the new struct members - int32_t error_reboot_count; //everytime we write this struct we increment this value by 1, irrespective of time between reboots. Note that the data itself might change, but everytime we reboot due to error we update this count by 1 + int32_t error_reboot_count; //every time we write this struct we increment this value by 1, irrespective of time between reboots. Note that the data itself might change, but every time we reboot due to error we update this count by 1 int32_t is_error_processed; //once this error is processed set this value to 1 uint32_t crc_error_ctx; //crc_error_ctx should always be the last member in this struct } mbed_error_ctx; diff --git a/platform/docs/memory-model/ram_memory_model.md b/platform/docs/memory-model/ram_memory_model.md index 1153716..88f7ba0 100644 --- a/platform/docs/memory-model/ram_memory_model.md +++ b/platform/docs/memory-model/ram_memory_model.md @@ -80,7 +80,7 @@ Phase 1 (5.12 Release): 1. Adopt 2-region memory model for Stack and Heap memory. -1. Unify the stack size accross all targets (RTOS: ISR stack - 1K Main thread Stack - 4K; Bare Metal(No RTOS) ISR/Main Stack - 4K) +1. Unify the stack size across all targets (RTOS: ISR stack - 1K Main thread Stack - 4K; Bare Metal(No RTOS) ISR/Main Stack - 4K) Phase 2: 1. Heap memory to be dynamic and starts at the end of ZI growing up till end of RAM memory (In case of single RAM bank) diff --git a/storage/filesystem/littlefs/littlefs/DESIGN.md b/storage/filesystem/littlefs/littlefs/DESIGN.md index 04a119f..640905f 100644 --- a/storage/filesystem/littlefs/littlefs/DESIGN.md +++ b/storage/filesystem/littlefs/littlefs/DESIGN.md @@ -624,7 +624,7 @@ directory not only contains pointers to all of its children, but also a pointer to the next directory. These pointers create a linked-list that is threaded through all of the directories in the filesystem. Because we -only use this linked list to check for existance, the order doesn't actually +only use this linked list to check for existence, the order doesn't actually matter. As an added plus, we can repurpose the pointer for the individual directory linked-lists and avoid using any additional space. diff --git a/tools/README.md b/tools/README.md index 8d1a571..104eedb 100644 --- a/tools/README.md +++ b/tools/README.md @@ -22,7 +22,7 @@ | `importer` | code importer for use with CMSIS, TFM/PSA etc. | | `libraries.py` | constants for building mbed 2 libraries | | `make.py` | implementation of `mbed compile` | -| `memap.py` | map file parser and sumary generator | +| `memap.py` | map file parser and summary generator | | `notifier` | API for seting compile status to a frontend | | `options.py` | Default option parser and option utilities | | `paths.py` | constants for many paths used |