diff --git a/component/main.jsonnet b/component/main.jsonnet
index 69e858e..a03204e 100644
--- a/component/main.jsonnet
+++ b/component/main.jsonnet
@@ -34,6 +34,11 @@ local machineSet = function(name, set)
           },
         },
         spec+: {
+          metadata+: {
+            labels+: {
+              'machine.openshift.io/cluster-api-machine-role': role,
+            },
+          },
           providerSpec+: {
             value+: {
               machineType: set.instanceType,
diff --git a/docs/modules/ROOT/pages/references/parameters.adoc b/docs/modules/ROOT/pages/references/parameters.adoc
index 1f780ab..1345ce6 100644
--- a/docs/modules/ROOT/pages/references/parameters.adoc
+++ b/docs/modules/ROOT/pages/references/parameters.adoc
@@ -5,9 +5,9 @@ The parent key for all of the following parameters is `openshift4_nodes`.
 [CAUTION]
 ====
 This component relies on deep merge of values from several parameters and hierarchy layers.
-This works pretty strait forward for scalar values and dictionaries.
+This works pretty straightforward for scalar values and dictionaries.
 Values of arrays will be appended to each other.
-There is no way to override values of set on lover precedence location.
+There is no way to override values which were set on a lower precedence location.
 ====
 
 == `availabilityZones`
@@ -52,8 +52,8 @@ See also https://github.com/appuio/component-openshift4-nodes/issues/2[Get a clu
 
 [TIP]
 ====
-This is most like to be configured on cluster level itself.
-Configuring that higher up in the hierarchy, can result in unexpected behavior.
+This is most likely to be configured on cluster level itself.
+Configuring this higher up in the hierarchy can result in unexpected behavior.
 ====
 
 == `namespace`
@@ -116,7 +116,7 @@ type:: string
 default:: worker
 
 The role of the created Nodes.
-The value will be added as the `node-role.kubernetes.io/<role>: ""` label to node.
+The value will be added as the `node-role.kubernetes.io/<role>: ""` label to nodes.
 
 [NOTE]
 ====