diff --git a/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md b/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md
index 49a77ef4..6822e18d 100644
--- a/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md
+++ b/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md
@@ -14,14 +14,14 @@ All jobs with an `x` in the boxes were performed to the best of knowledge.
 ## Pre-Merge Activities
 <!--- Lets check everything before we continue. -->
 - [ ] This PR refers to a versioned Branch with a name and a version number in the form of N.n.n, e.g. "TC_3.2.1".
-- [ ] This PR has a clean meaningful committ history. Minor committs or committs without descirption have been squashed, at the latest now.
-- [ ] The _./github/workflows/main.yml_ refers to the correct Firetly Terminal and SUSHI Version. 
+- [ ] This PR has a clean meaningful commit history. Minor commits or commits without description have been squashed, at the latest now.
+- [ ] The _./github/workflows/main.yml_ refers to the correct Firely Terminal and SUSHI Version. 
     > **_Firely Terminal Pipeline_**  0.4.0.
 
     > **_SUSHI Versions_**  3.5.0.
 - [ ] By running the _Release_Publish.py_ script, release version and date was updated accordingly. The script ran without errors.
 - [ ] Eventually, increase the dependency of to newer Basis Modul (package and sushi-config)
-- [ ] New Release Notes were created, aglined to the committ history and cleaned. In Github, go to 
+- [ ] New Release Notes were created, alined to the commit history and cleaned. In Github, go to 
   - [ ]  _-> Releases_ then _-> Draft a new release_ with the _Modul Name and Version_, then
   - [ ] _-> Target the main-Branch_ and _->enter a new Tag according to the Version_, then click.
   - [ ] Click _-> Generate Release notes_ , _->Adjust them if necessary_ and _-> Copy/Paste the Details in the RealeaseNotes.md_ of the very Branch you want to merge.
@@ -32,7 +32,7 @@ All jobs with an `x` in the boxes were performed to the best of knowledge.
 <!--- Include details of your testing environment, especially -->
 - [ ] With the updated Version, Dates, and Release Notes (as described above) with the last committ into the Branch you want to merge.
 - [ ] In GitHub _-> Actions_ the _->CI (FHIR Validation)_ workflow terminates successfully.
-- [ ] Add the Approve / the PR gets posivitly reviewed by a collegue.
+- [ ] Add the Approve / the PR gets positively reviewed by a colleague.
 - [ ] Merge (without squash) the PR, delete the Branch.
 
 
@@ -43,15 +43,15 @@ All jobs with an `x` in the boxes were performed to the best of knowledge.
 - [ ] Go to the corresponding SIMPLIFIER Project and _-> Packages -> Expand the Dropdown for Create -> Create new package_ for the project.
   - [ ] With the corresponding version number, and
   - [ ] The Release notes (from above) and a compare-link to the previous Release.
-  - [ ] Unlist the old package by _-> clicking on the old package_, _-> go to Admininstration_ and _-> click on Unlist_
-- [ ] Publish the previosuly drafteted Release, including version number, on GitHub.
+  - [ ] Unlist the old package by _-> clicking on the old package_, _-> go to Administration_ and _-> click on Unlist_
+- [ ] Publish the previously drafted Release, including version number, on GitHub.
 - [ ] Provide / Archive the IG in the corresponding _gh-pages_ branch of the GitHub project.
   - [ ] Checkout the Branch (no need to merge it later).
   - [ ] Export from Simplifier via _-> Guides -> Expand the Modul ... -> Export_
-  - [ ] Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version coressponding) new folder in the branch folder structure.
+  - [ ] Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version corresponding) new folder in the branch folder structure.
   - [ ] Update the file index.html and check rendering
-  - [ ] committ the branch.
-- [ ] If ISiK Basismodul was updated all depending Modules should be updated  with a newed dependency to the incremented Basismodul version - possibly including and closing technical corrections
+  - [ ] commit the branch.
+- [ ] If ISiK Basismodul was updated all depending Modules should be updated  with a renewed dependency to the incremented Basismodul version - possibly including and closing technical corrections
 
 
 ## Finished