Remove trailing whitespaces

Author: AniruddhaKanhere

.github/workflows/ci.yml

@@ -46,7 +46,7 @@ jobs:
       #    path: "build/coverage.info"
       #    min_coverage: 99
       #    exclude: "**/*test*"
-    
+
   formatting:
     runs-on: ubuntu-latest
     steps:

CONTRIBUTING.md

@@ -17,7 +17,7 @@ If you discover a potential security issue in this project we ask that you notif
 
 ## Submitting a bugs/feature request
 Have a bug to report or feature to request? Follow these steps:
-1. Search on the [FreeRTOS Community Support Forums](https://forums.freertos.org/) and [GitHub issue tracker](https://github.com/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't been already reported or discussed. 
+1. Search on the [FreeRTOS Community Support Forums](https://forums.freertos.org/) and [GitHub issue tracker](https://github.com/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't been already reported or discussed.
 2. If your search turns up empty, create a new topic in the [forums](https://forums.freertos.org/) and work with the community to help clarify issues or refine the idea. Include as many of the details listed below.
 3. Once the community has had time to discuss and digest, we welcome you to create an [issue](https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/issues) to report bugs or suggest features.
 
@@ -43,8 +43,8 @@ To send us a pull request, please:
 2. Modify the source; focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
 3. Follow the [coding style guide](https://www.freertos.org/FreeRTOS-Coding-Standard-and-Style-Guide.html).
 4. Commit to your fork using clear commit messages.
-5. Send us a pull request, answering any default questions in the pull request interface.    
-   NOTE: Please make sure the default option (Allow edits from maintainers) is left checked.    
+5. Send us a pull request, answering any default questions in the pull request interface.
+   NOTE: Please make sure the default option (Allow edits from maintainers) is left checked.
 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and

History.txt

@@ -37,7 +37,7 @@ Changes between V2.0.0 and V2.2.1 releases:
 	  when the ID in the reply comes from the device.
 
 Changes between 180821 and V2.0.0 releases:
-	+ Move the TCP source code from FreeRTOS/FreeRTOS-Labs to FreeRTOS/FreeRTOS 
+	+ Move the TCP source code from FreeRTOS/FreeRTOS-Labs to FreeRTOS/FreeRTOS
 	  repository.
 
 Changes between 160919 and 180821 releases:

SECURITY.md

@@ -1,5 +1,5 @@
 ## Reporting a Vulnerability
 
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security 
-via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [email protected]. 
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security
+via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [email protected].
 Please do **not** create a public github issue.

portable/Compiler/CompilerName/ReadMe.txt

@@ -1,3 +1,3 @@
 Update pack_struct_start.h and pack_struct_end.h for your architecure.
-These files define the specifiers needed by your compiler to properly pack struct data 
-need by FreeRTOS+TCP.
+These files define the specifiers needed by your compiler to properly pack struct data
+need by FreeRTOS+TCP.

portable/NetworkInterface/STM32Fxx/readme.txt

@@ -55,14 +55,14 @@ As long as the part has no caching, this section can be placed anywhere in RAM.
 On an STM32F7 with an L1 data cache, it shall be placed in the first 64KB of RAM, which is always uncached.
 The linker script must be changed for this, for instance as follows:
 
-   .data : 
+   .data :
    {
      . = ALIGN(4);
      _sdata = .;        // create a global symbol at data start
 +    *(.first_data)     // .first_data sections
      *(.data)           // .data sections
      *(.data*)          // .data* sections
- 
+
      . = ALIGN(4);
      _edata = .;        // define a global symbol at data end
    } >RAM AT> FLASH

test/cbmc/proofs/CMakeLists.txt

@@ -17,7 +17,7 @@ list(APPEND cbmc_compile_includes
     ${CMAKE_SOURCE_DIR}/Source/include
     ${CMAKE_SOURCE_DIR}/Source/portable/MSVC-MingW
 	${CMAKE_SOURCE_DIR}/Source/../../FreeRTOS-Plus/Source/FreeRTOS-Plus-TCP/portable/BufferManagement
-	${CMAKE_SOURCE_DIR}/Source/../../FreeRTOS-Plus/Source/FreeRTOS-Plus-TCP/include    
+	${CMAKE_SOURCE_DIR}/Source/../../FreeRTOS-Plus/Source/FreeRTOS-Plus-TCP/include
     ${CMAKE_SOURCE_DIR}/Source/../../FreeRTOS-Plus/Source/FreeRTOS-Plus-TCP/portable/Compiler/MSVC
     ${cbmc_dir}/include
     ${cbmc_dir}/windows

tools/tcp_dump_packets.md

@@ -48,7 +48,7 @@ Here is some contents of the output file:
     /*-----------------------------------------------------------*/
 
 tcp_dump_packets has an enum of all possible properties of network packets:
-    ICMP4, ICMP6, UDP, TCP, DNS, REPLY, REQUEST, SYN, 
+    ICMP4, ICMP6, UDP, TCP, DNS, REPLY, REQUEST, SYN,
     FIN, RST, ACK, IN, OUT, ARP, FRAME_ARP, FRAME_4, and FRAME_6
 
 Each property is defined as a bit so they can be combined as in: