Typo

README.md

@@ -6,21 +6,21 @@
 
 # Objective 
 
-This project intend to allow everyone to create cheatsheet without programming skills.
-The main objectives are :
- - Build a **easy-to-use** and **easy-to-maintain** engine to generate cheatsheets
- - Use the well known **markdown** format to create it
- - Offer a way to create and use different **templates** to render document
- - Automatically build a website with all created cheatsheets
- - Allow to export it as a simple recto-verso PDF
+This project intends to allow everyone to create cheatsheets without programming skills.
+The main objectives are:
+ - Build a **easy-to-use** and **easy-to-maintain** engine to generate cheatsheets.
+ - Use the well known **markdown** format to create it.
+ - Offer a way to create and use different **templates** to render documents.
+ - Automatically build a website with the newly created cheatsheet.
+ - Allow to export it as a simple recto-verso PDF.
 
 ![workflow](https://github.com/zenika-open-source/cheatsheets/blob/main/workflow.png?raw=true)
 
 ## Live demo
-You can explore a live demo of this project [here](https://zenika-open-source.github.io/cheatsheets/)
+You can explore a live demo of this project [here](https://zenika-open-source.github.io/cheatsheets/).
 
 ## Quick Start
-To create your very first cheatsheets, follow this [Quick Start Guide](https://zenika-open-source.github.io/cheatsheets/quick-start/) 
+To create your very first cheatsheets, follow this [Quick Start Guide](https://zenika-open-source.github.io/cheatsheets/quick-start/).
 
 ## Template Configuration
 Cheatsheets are generated from Markdown files located in the `cheatsheets` folder. To configure the template and styles used in generating the Markdown, please refer to the `config.json` file. To understand how it works and how you can configure it, please follow the [Template Grid Flow](https://zenika-open-source.github.io/cheatsheets/template-grid-flow/).

cheatsheets/conventional-commit/index.md

@@ -1,6 +1,6 @@
 ::: column
 
-# What is it ?
+# What is it?
 
 A Conventional Commit is a standardized way of writing commit messages in version control systems like Git. It follows a specific format to make it easier to understand the purpose and scope of each commit. The Conventional Commit format is commonly used in projects that follow semantic versioning (semver) and use tools like Lerna to automate the release process.
 
@@ -19,7 +19,7 @@ Here's a cheatsheet to help you understand and use Conventional Commits:
 # Types
 
 - **feat**: A new feature or functionality added to the project.
-- **fix**: A bug fix or correction to existing code.
+- **fix**: A bugfix or correction to existing code.
 - **chore**: Routine tasks, maintenance, or non-functional changes.
 - **docs**: Documentation updates or additions.
 - **style**: Code style, formatting, or whitespace changes (not affecting the code's behavior).

cheatsheets/esp32/index.md

@@ -9,7 +9,7 @@
 | - WiFi 2.4Ghz      | - Analog GPIO            |
 | - Bluetooth        | - Touch sensor           |
 | - 240Mhz dual core | - Hall sensor            |
-| - Digital GPIO     | - I2C, SPI, SD, UART,... |
+| - Digital GPIO     | - I2C, SPI, SD, UART . . . |
 
 
 # GPIOs digital specificities
@@ -109,7 +109,7 @@ void loop() {
   }
   Serial.print("Hello");
   Serial.println(" World");
-  // Not mandatory, wait for transmission finish
+  // Not mandatory, wait for transmission to finish
   Serial.flush();
 }
 ```
@@ -123,7 +123,7 @@ interrupts(); // re-enable all interruptions
 ```
 
 # Mutli threading
-/!\ do not overload core 0, this core control WiFi
+/!\ do not overload core 0 as it controls WiFi
 
 ```cpp
 // core: 0 or 1
@@ -132,7 +132,7 @@ xTaskCreatePinnedToCore(taskFunc, threadName, stackSize,
                         parameters, priority, &taskRef, core);
 vTaskDelete(taskRef);
 
-// example :
+// example:
 TaskHandle_t myThreadTask;
 xTaskCreatePinnedToCore(myThread, "My thread", 10000, 
                         NULL, 2, &myThreadTask, 0);
@@ -235,9 +235,9 @@ void loop() {
 ```
 
 
-Note that `server.handleClient();` is mandatory to tell the lib to check network stack request buffer.
+Note that `server.handleClient();` is mandatory to tell the lib to check the network stack request buffer.
 
-Otherwise, request from clients will not be accept.
+Otherwise, request from clients will not be accepted.
 
 The longer the delay between `handleClient` the longer the request connection will take.
 :::