Add Platform Labeler example (#248)

* Add Platform Labeler example to docs

Combining the implied labels plugin and platform labeler plugin can
simplify label management for agents that intentionally vary by operating
system or processor architecture.

* Remove first Platform Labeler reference

README.md

@@ -29,7 +29,6 @@ labels contributed by other implications.
 ## Configuration as code
 
 Label definitions can be automated with [configuration as code](https://plugins.jenkins.io/configuration-as-code/).
-The [platform labeler](https://plugins.jenkins.io/platformlabeler/) can automatically assign labels based on operating system properties and those operating system properties can be used to define more labels.
 
 ```
 unclassified:
@@ -38,3 +37,26 @@ unclassified:
     - atoms: "linux"
       expression: "Ubuntu || CentOS || Debian || Rocky || openSUSE"
 ```
+
+When combined with the [Platform Labeler plugin](https://plugins.jenkins.io/platformlabeler/), the implied labels can use the labels generated by the Platform Labeler plugin.
+Here is an example that combines the two plugins to apply the `linux` label to an operating system based on its name.
+
+```yaml
+unclassified:
+  impliedLabels:
+    implications:
+    - atoms: "linux"
+      expression: "Alpine||Amazon||Debian||Fedora||openSUSE||Raspbian||RedHatEnterprise||Rocky||SUSE||Ubuntu"
+    - atoms: "Unix"
+      expression: "linux||freebsd"
+  platformLabelerGlobalConfiguration:
+    labelConfig:
+      architecture: true
+      architectureName: false
+      architectureNameVersion: false
+      name: true
+      nameVersion: false
+      osName: true
+      version: true
+      windowsFeatureUpdate: false
+```