Fix typos in the documentation and related files (#4809)

JerryScript-DCO-1.0-Signed-off-by: Zsolt Borbély zsborbely.u-szeged@partner.samsung.com

4 files changed, 7 insertions, 7 deletions

diff --git a/targets/curie_bsp/README.md b/targets/curie_bsp/README.md
index 8e1e70ab..967782a7 100644
--- a/targets/curie_bsp/README.md
+++ b/targets/curie_bsp/README.md
@@ -6,7 +6,7 @@ This folder contains necessary files to integrate JerryScript with Intel® Curie
 ### How to build
 #### 1. Preface
 
-Curie BSP only support Ubuntu GNU/Linux as host OS envirenment.
+Curie BSP only support Ubuntu GNU/Linux as host OS environment.
 
 Necessary hardwares
 * [FlySwatter2 JTAG debugger](https://www.tincantools.com/wiki/Flyswatter2)
@@ -117,4 +117,4 @@ undefined
 js e 1 OK
 ```
 
-`js e 1 ACK` and `js e 1 OK` are debug info of Curie BSP uart commands, which mean it receive and execute the command sucessfully. `Hello World!` is the printed content. `undefined` is the return value of the statement `print ('Hello World!')`.
+`js e 1 ACK` and `js e 1 OK` are debug info of Curie BSP uart commands, which mean it receive and execute the command successfully. `Hello World!` is the printed content. `undefined` is the return value of the statement `print ('Hello World!')`.
diff --git a/targets/esp-idf/README.md b/targets/esp-idf/README.md
index a61b85f7..2b4d385c 100644
--- a/targets/esp-idf/README.md
+++ b/targets/esp-idf/README.md
@@ -4,9 +4,9 @@ This is a port for espressif's esp-idf (esp32). The MATH, LTO and STRIP options
 python tools\build.py --toolchain=cmake/toolchain-esp32.cmake --cmake-param "-GUnix Makefiles" --jerry-cmdline=OFF --jerry-port-default=OFF --lto=OFF --strip=OFF
 ```
 
-NB: the MATH, STRIP and LTO might be disabled by platform as well. I strongly suggest limiting heap memorry with '--mem-heap=128' but that really depends on the SRAM avaiulable on your esp32.
+NB: the MATH, STRIP and LTO might be disabled by platform as well. I strongly suggest limiting heap memory with '--mem-heap=128' but that really depends on the SRAM available on your esp32.
 
-Then copy the artefacts 'build/lib/\*.a' in an esp-idf component named 'jerryscript' (eg) and use a 'CMakeLists.txt' like this one
+Then copy the artifacts 'build/lib/\*.a' in an esp-idf component named 'jerryscript' (eg) and use a 'CMakeLists.txt' like this one
 
 ```
 # assumes there is a component with this the following
diff --git a/targets/openwrt/readme.md b/targets/openwrt/readme.md
index f51bbc08..60a342fb 100644
--- a/targets/openwrt/readme.md
+++ b/targets/openwrt/readme.md
@@ -8,7 +8,7 @@ modifications to this document could be required.
 IMPORTANT!
 
 As the TP-Link WR1043ND is a mips based device and mips is a big-endian
-architecture a JerryScipt snapshot which was built on an little-endian
+architecture a JerryScript snapshot which was built on an little-endian
 system will not work correctly. Thus it is advised that the
 snapshot functionally should be used with caution, that is
 DO NOT run snapshots generated on little-endian system(s) on
diff --git a/targets/zephyr/README.md b/targets/zephyr/README.md
index 049ed1f0..8e52f016 100644
--- a/targets/zephyr/README.md
+++ b/targets/zephyr/README.md
@@ -39,7 +39,7 @@ If you just start with Zephyr, you may want to follow "Building a Sample
 Application" section in the doc above and check that you can flash your
 target board.
 
-Remember to source the Zephyr environment as explained in the zephyr documenation:
+Remember to source the Zephyr environment as explained in the zephyr documentation:
 
 ```
 cd zephyr-project
@@ -71,7 +71,7 @@ Below, we build for NXP FRDM-K64F board (`frdm_k64f` Zephyr board
 identifier). Building for other boards is similar. You are expected
 to read [Supported Boards](https://docs.zephyrproject.org/latest/boards/index.html)
 section in the Zephyr documentation for more information about
-Zephyr's support for a particilar board, means to flash binaries,
+Zephyr's support for a particular board, means to flash binaries,
 etc.
 
 ```