diff --git a/data/presets/highway/crossing/README.md b/data/presets/highway/crossing/README.md
index 565e5b80..7a04daf1 100644
--- a/data/presets/highway/crossing/README.md
+++ b/data/presets/highway/crossing/README.md
@@ -3,17 +3,17 @@
 ## General
 
 These presets use fields `@templates` to make sure all have a similar structure.
-Some presets like `traffic_signals` have additinal fields and use a different field order.
+Some presets like `traffic_signals` have additional fields and use a different field order.
 Try to keep the file structure very similar so they can be easily compared.
 
 ## nodes `highway=crossing + crossing=*`
 
-Crossing nodes are handel by `highway/crossing.json` + `highway/crossing/*.json` (as geometry type `vertex`).
+Crossing nodes are handled by `highway/crossing.json` and `highway/crossing/*.json` (as geometry type `vertex`).
 
 Crossing nodes and crossing ways have a big overlap.
-However, there are a few tags that should _only_ be expected on the crossing node. When crossing ways are present, this also means there are separate ways attached with additional nodes that hald the
+However, there are a few tags that should _only_ be expected on the crossing node. When crossing ways are present, this also means there are separate ways attached with additional nodes that may hold these additional tags.
 
-There are places in OSM that follow a different tagging style where only crossing ways are used (without the vertex nodes). Those regions might have other conventions on where to place
+There are places in OSM that follow a different tagging style where only crossing ways are used (without the vertex nodes). Those regions might use other conventions on where to place each tag.
 
 ## ways `highway=footway|cycleway|path + *=crossing + crossing=*`