Simple spelling fixes (#2496)

docs/get-started/arduino.md

@@ -39,9 +39,9 @@ LVGL has its own configuration file called `lv_conf.h`. When LVGL is installed t
 Take a look at [LVGL_Arduino.ino](https://github.com/lvgl/lvgl/blob/master/examples/arduino/LVGL_Arduino/LVGL_Arduino.ino) to see how to initialize LVGL.
 TFT_eSPI is used as the display driver.
 
-In the INO file you can see how to register a display and a touch pad for LVGL and call an example.
+In the INO file you can see how to register a display and a touchpad for LVGL and call an example.
 
-Note that, there is no dedicated INO file for every example but you can call functions like `lv_example_btn_1()` or `lv_example_slider_1()` to run an example.
+Note that, there is no dedicated INO file for every example, but you can call functions like `lv_example_btn_1()` or `lv_example_slider_1()` to run an example.
 Most of the examples are available in the [`lvgl/examples`](https://github.com/lvgl/lvgl/tree/master/examples) folder. Some are also available in [`lv_demos`](https://github.com/lvgl/lv_demos), which needs to be installed and configured separately.
 
 ## Debugging and logging

docs/get-started/micropython.md

@@ -26,7 +26,7 @@ Currently, Micropython [does not have a good high-level GUI library](https://for
 
 ### Here are some advantages of using LVGL in Micropython:
 
-- Develop GUI in Python, a very popular high level language. Use paradigms such as Object Oriented Programming.
+- Develop GUI in Python, a very popular high level language. Use paradigms such as Object-Oriented Programming.
 - Usually, GUI development requires multiple iterations to get things right. With C, each iteration consists of **`Change code` > `Build` > `Flash` > `Run`**.  
 In Micropython it's just **`Change code` > `Run`** ! You can even run commands interactively using the [REPL](https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop) (the interactive prompt)
 
@@ -44,7 +44,7 @@ This goes well with [CircuitPython vision](https://learn.adafruit.com/welcome-to
 ## So what does it look like?
 
 > TL;DR:
-> It's very much like the C API, but Object Oriented for LVGL components.
+> It's very much like the C API, but Object-Oriented for LVGL components.
 
 Let's dive right into an example!  
 

docs/get-started/nuttx.md

@@ -12,9 +12,9 @@ The best way to think about NuttX is to think of it as a small Unix/Linux for mi
 
 ### Highlights of NuttX
 
-- **Small** - Fits and runs in microcontrollers as small as 32KB Flash and 8KB of RAM.
+- **Small** - Fits and runs in microcontrollers as small as 32 kB Flash and 8 kB of RAM.
 - **Compliant** - Strives to be as compatible as possible with POSIX and Linux.
-- **Versatile** - Supports many architectures (ARM, ARM Thumb, AVR, MIPS, OpenRISC, RISC-V 32-bit and 64-bit, RX65N, x86-64, Xtensa, Z80/Z180, etc).
+- **Versatile** - Supports many architectures (ARM, ARM Thumb, AVR, MIPS, OpenRISC, RISC-V 32-bit and 64-bit, RX65N, x86-64, Xtensa, Z80/Z180, etc.).
 - **Modular** - Its modular design allows developers to select only what really matters and use modules to include new features.
 - **Popular** - NuttX is used by many companies around the world. Probably you already used a product with NuttX without knowing it was running NuttX.
 - **Predictable** - NuttX is a preemptible Realtime kernel, so you can use it to create predictable applications for realtime control.
@@ -56,7 +56,7 @@ Let's use the [Windows Subsystem for Linux](https://acassis.wordpress.com/2018/0
 $ sudo apt-get install automake bison build-essential flex gcc-arm-none-eabi gperf git libncurses5-dev libtool libusb-dev libusb-1.0.0-dev pkg-config kconfig-frontends openocd
 ```
 
-### Now let's to create a workspace to save our files
+### Now let's create a workspace to save our files
 
 ```shell
 $ mkdir ~/nuttxspace

docs/get-started/pc-simulator.md

@@ -9,7 +9,7 @@ You can try out LVGL **using only your PC** (i.e. without any development boards
 
 Using the simulator on the PC has the following advantages:
 - Hardware independent - Write code, run it on the PC and see the result on the PC monitor.
-- Cross-platform - Any Windows, Linux or MacOS system can run the PC simulator.  
+- Cross-platform - Any Windows, Linux or macOS system can run the PC simulator.  
 - Portability - the written code is portable, which means you can simply copy it when using an embedded hardware.
 - Easy Validation - The simulator is also very useful to report bugs because it means common platform for every user. So it's a good idea to reproduce a bug in the simulator and use the code snippet in the [Forum](https://forum.lvgl.io).
 
@@ -45,7 +45,7 @@ You can download Eclipse's CDT from: [https://www.eclipse.org/cdt/downloads.php]
 
 ### Install SDL 2
 
-The PC simulator uses the [SDL 2](https://www.libsdl.org/download-2.0.php) cross platform library to simulate a TFT display and a touch pad. 
+The PC simulator uses the [SDL 2](https://www.libsdl.org/download-2.0.php) cross-platform library to simulate a TFT display and a touchpad. 
 
 #### Linux
 On **Linux** you can easily install SDL2 using a terminal:
@@ -82,16 +82,16 @@ You can find the latest one on [GitHub](https://github.com/lvgl/lv_sim_eclipse_s
 
 Run Eclipse CDT. It will show a dialogue about the **workspace path**. Before accepting the path, check that path and copy (and unzip) the downloaded pre-configured project there. After that, you can accept the workspace path. Of course you can modify this path but, in that case copy the project to the corresponding location.
 
-Close the start up window and go to **File->Import** and choose **General->Existing project into Workspace**. **Browse the root directory** of the project and click **Finish**
+Close the start-up window and go to **File->Import** and choose **General->Existing project into Workspace**. **Browse the root directory** of the project and click **Finish**
 
 On **Windows** you have to do two additional things:
 
 - Copy the **SDL2.dll** into the project's Debug folder 
-- Right click on the project -> Project properties -> C/C++ Build -> Settings -> Libraries -> Add ... and add _mingw32_ above SDLmain and SDL. (The order is important: mingw32, SDLmain, SDL)
+- Right-click on the project -> Project properties -> C/C++ Build -> Settings -> Libraries -> Add ... and add _mingw32_ above SDLmain and SDL. (The order is important: mingw32, SDLmain, SDL)
 
 ### Compile and Run
 
-Now you are ready to run LVGL on your PC. Click on the Hammer Icon on the top menu bar to Build the project. If you have done everything right, then you will not get any errors. Note that on some systems additional steps might be required to "see" SDL 2 from Eclipse but, in most of cases the configurations in the downloaded project is enough.
+Now you are ready to run LVGL on your PC. Click on the Hammer Icon on the top menu bar to Build the project. If you have done everything right, then you will not get any errors. Note that on some systems additional steps might be required to "see" SDL 2 from Eclipse but, in most cases the configuration in the downloaded project is enough.
 
 After a success build, click on the Play button on the top menu bar to run the project. Now a window should appear in the middle of your screen.
 

docs/get-started/quick-overview.md

@@ -59,7 +59,7 @@ void my_disp_flush(lv_disp_drv_t * disp, const lv_area_t * area, lv_color_t * co
 }
 
 ```
-- Implement and register a function which can read an input device. E.g. for a touch pad:
+- Implement and register a function which can read an input device. E.g. for a touchpad:
 ```c
 static lv_indev_drv_t indev_drv;           /*Descriptor of a input device driver*/
 lv_indev_drv_init(&indev_drv);             /*Basic initialization*/
@@ -94,7 +94,7 @@ Every object has a parent object where it is created. For example if a label is
 
 The child object moves with the parent and if the parent is deleted the children will be deleted too. 
 
-Children can be visible only on their parent. It other words, the parts of the children outside of the parent are clipped.
+Children can be visible only on their parent. In other words, the parts of the children outside the parent are clipped.
 
 A Screen is the "root" parent. You can have any number of screens. 
 
@@ -142,7 +142,7 @@ void btn_event_cb(lv_event_t * e)
 
 Instead of `LV_EVENT_CLICKED` `LV_EVENT_ALL` can be used too to call the callback for any event. 
 
-From `lv_event_t * e` the current event code can be get with
+From `lv_event_t * e` the current event code can be retrieved with
 ```c
 lv_event_code_t code = lv_event_get_code(e);
 ```
@@ -185,9 +185,9 @@ lv_obj_clear_state(obj, LV_STATE_...);
 ```
 
 ### Styles
-Styles contains properties such as background color, border width, font, etc to describe the appearance of the objects.
+Styles contains properties such as background color, border width, font, etc. to describe the appearance of the objects.
 
-The styles are `lv_style_t` variables. Only their pointer is saved in the objects so they need to be static or global.
+The styles are `lv_style_t` variables. Only their pointer is saved in the objects, so they need to be static or global.
 Before using a style it needs to be initialized with `lv_style_init(&style1)`. After that properties can be added. For example:
 ```
 static lv_style_t style1;