Merge pull request #13532 from Pa-Touche/patch-1

Corrected typos

Author: SORMAS-JanBoehme

sormas-app/README.md

@@ -4,7 +4,7 @@ The SORMAS Android app is designed for use by users at the level of hospitals, c
 These have only limited access to the overall data of the system, so it is possible to transfer the relevant data set and make it available offline.
 
 The **offline** functionality was also one of the core requirements in the development of the app, as it is also to be used in areas where no or hardly any mobile data network is available.
-This makes it possible for users to use the app freely and, for example, to synchronise the recorded data with the server in the evening.
+This makes it possible for users to use the app freely and, for example, to synchronize the recorded data with the server in the evening.
 
 The app covers **all essential functionalities of SORMAS** and the complete data collection in the areas of
 cases, contacts, events, samples, messages, aggregate reports and tasks.
@@ -14,9 +14,9 @@ To manage the large number of devices used within a country and to simplify supp
 
 ## Data Synchronization
 
-For synchronisation, the Android app accesses the **SORMAS ReST** interface.
+For synchronization, the Android app accesses the **SORMAS ReST** interface.
 
-First, all data that has changed since the last synchronisation is retrieved from the server.
+First, all data that has changed since the last synchronization is retrieved from the server.
 In the app, a three-way merge takes place for all data that the user has changed himself in the meantime.
 For each individual field (e.g. gender of a person), it is checked whether the value on the server has changed compared to the original status on the device.
 If so, this change is adopted, otherwise any existing change of the user is retained.
@@ -48,7 +48,7 @@ During the update **existing data is automatically migrated** using the commands
 
 ## Device Encryption
 
-Each Android device using SORMAS should ahve device encryption enabled. This is currently not enforced.
+Each Android device using SORMAS should have device encryption enabled. This is currently not enforced.
 
 ## Data Storage
 

sormas-backend/README.md

@@ -1,6 +1,6 @@
 # SORMAS Backend
 
-The SORMAS backend layer is the implementation of the `sormas-api` and gives access to the data and logic of SORMAS. It contains a big set of facades and services that are origanized based on the different entities and their domains, like case surveillance and contact tracing.
+The SORMAS backend layer is the implementation of the `sormas-api` and gives access to the data and logic of SORMAS. It contains a big set of facades and services that are organized based on the different entities and their domains, like case surveillance and contact tracing.
 
 ## Unit Testing
 
@@ -23,7 +23,7 @@ Most important:
 This means you can make full use of cdi annotations like `@Inject`.
 
 #### Enterprise Beans (EJB)
-cdi-test imitates this by adding cdi annotations to classes annotated with bean annotiations like `@Stateless`.\
+cdi-test imitates this by adding cdi annotations to classes annotated with bean annotations like `@Stateless`.\
 This means all EJB classes can be used in test classes by injecting them.
 
 You can **mock beans** as explained here: [Mocking Beans](https://cdi-test.hilling.de/#mocking-beans)\

sormas-performance-gatling/README.md

@@ -2,4 +2,4 @@ To trigger execution of tests, please use the following command:
 
 `./mvnw gatling:test -DenvConfig=myPath/envData.json -Denv=performance -Dusers=10 -Dtime=10`
 
-./mvnw gatling:test -DenvConfig=path-to/envData.json -Denv=performance -Dusers=1 -Dtime=1
+`./mvnw gatling:test -DenvConfig=path-to/envData.json -Denv=performance -Dusers=1 -Dtime=1`

sormas-rest/README.md

@@ -84,7 +84,7 @@ The follow-up status describes the follow-up for a contact or a case. Possible v
 [the FollowUpStatus enum](https://github.com/sormas-foundation/SORMAS-Project/blob/development/sormas-api/src/main/java/de/symeda/sormas/api/contact/FollowUpStatus.java)
 
 Follow up can be done with, or without an external journal, the follow-up status makes no distinction there. Because the
-follow-up status is contact and case specific,but the communication with external journals is person based, SORMAS
+follow-up status is contact and case specific, but the communication with external journals is person based, SORMAS
 determines the most important follow-up status of all contacts and cases related to the person in question when
 communicating with external journals. Whenever there is follow-up ongoing for any of the persons contacts (and cases if
 the case follow-up feature is enabled in SORMAS), SORMAS will state the `FollowUpStatus.FOLLOW_UP` for that person
@@ -163,7 +163,7 @@ supervisor, contact officer, community officer, surveillance officer, surveillan
 
 First comes a SORMAS-internal validation of contact details.
 The person to be registered needs to have at least an email address (or a phone number if that is accepted for
-registration, see `interface.patientdiary.acceptPhoneContact`) to pass this validation.Also, when there are several
+registration, see `interface.patientdiary.acceptPhoneContact`) to pass this validation. Also, when there are several
 email addresses or phone numbers, one of them has to be marked primary contact detail, so that it is clear which contact
 detail shall be used.