Fix typos in external message data mismatch notifications

Author: raulbob

sormas-api/src/main/resources/strings.properties

@@ -1073,12 +1073,12 @@ infoPersonMergeSharedMustLead = Please note, you cannot choose this person as a
 infoPickEventParticipantsForPersonMerge = The selected persons both have one event participant in at least one event. Merging the persons would lead to duplicate event participants.<br/> For each event, please select one of the event participants below as the leading event participant.<br/> 'Merge': The discarded event participant will be removed from the event. Its associated entities and information will be linked and/or added to the remaining event participant, but not overwritten. You will not be able to undo this action.<br/> 'Pick': The discarded event participant will be removed from the event. Its associated entities and information will not be linked and/or added to the remaining event participant. You will not be able to undo this action.
 infoPickorMergeEventParticipantDuplicateEventParticipantByPersonByEvent = One of the selected persons has multiple active or archived event participants in the same event(s).<br/>Please review the events with the UUIDs presented below and delete duplicate event participants or ask a supervisor to do so in order to be able to merge these persons.
 infoPersonMergeConfirmationForNonSimilarPersons = The two selected persons do not match the similarity requirements used by SORMAS to detect duplicate persons. Please ensure that the selected persons are indeed identical and supposed to be merged before proceeding.
-infoExternalMessageCaseSymptomsMismatch = The symptoms in the doctor declaration differ from the selected case.<br/>The incomming values will not be transfered.<br/>Do you wish to continue?
+infoExternalMessageCaseSymptomsMismatch = The symptoms in the doctor declaration differ from the selected case.<br/>The incoming values will not be transferred.<br/>Do you wish to continue?
 infoExternalMessageCaseSymptomsMismatchExistingCaseSymptoms = Existing case symptoms: %s
 infoExternalMessageCaseSymptomsMismatchExternalMessageSymptoms = External message symptoms: %s
-infoExternalMessageCaseHospitalizationMismatch = The hospitalization information in the doctor declaration differs from the selected case.<br/>The incomming values will not be transfered.<br/>Do you wish to continue?
-infoExternalMessageCaseExposuresMismatch = The exposures in the doctor declaration differ from the selected case.<br/>The incomming values will not be transfered.<br/>Do you wish to continue?
-infoExternalMessageCaseActivitiesAsCaseMismatch = The activities as case in the doctor declaration differ from the selected case.<br/>The incomming values will not be transfered.<br/>Do you wish to continue?
+infoExternalMessageCaseHospitalizationMismatch = The hospitalization information in the doctor declaration differs from the selected case.<br/>The incoming values will not be transferred.<br/>Do you wish to continue?
+infoExternalMessageCaseExposuresMismatch = The exposures in the doctor declaration differ from the selected case.<br/>The incoming values will not be transferred.<br/>Do you wish to continue?
+infoExternalMessageCaseActivitiesAsCaseMismatch = The activities as case in the doctor declaration differ from the selected case.<br/>The incoming values will not be transferred.<br/>Do you wish to continue?
 infoHowToMergeCases = You can choose between two options when reviewing potentially duplicate cases:
 infoHowToMergeContacts = You can choose between two options when reviewing potentially duplicate contacts:
 infoCalculateCompleteness = The <i>Calculate Completeness</i> button on top can be used to calculate the completeness values for all cases in the table. This is only necessary if there are cases in the list that do not yet have a completeness value. Normally, this value is automatically updated whenever the details of a case or one of its contacts or samples change.