Tweak label readme and fix generic label example

Signed-off-by: Tuomas Katila <[email protected]>

Author: tkatila

cmd/gpu_plugin/labels.md

@@ -4,11 +4,11 @@ GPU labels originate from two main sources: NFD rules and GPU plugin (& NFD hook
 
 ## NFD rules
 
-NFD rule is a method to instruct NFD to add certain label(s) to node based on the devices detected on it. There is a generic rule to identify all Intel GPUs. It will add labels for each pci device type. For example, a Tigerlake iGPU will show up as:
+NFD rule is a method to instruct NFD to add certain label(s) to node based on the devices detected on it. There is a generic rule to identify all Intel GPUs. It will add labels for each PCI device type. For example, a Tigerlake iGPU (PCI Id 0x9a49) will show up as:
 
 ```
-gpu.intel.com/device-id-0300-9a49.count=1
-gpu.intel.com/device-id-0300-9a49.present=true
+gpu.intel.com/device-id.0300-9a49.count=1
+gpu.intel.com/device-id.0300-9a49.present=true
 ```
 
 For data center GPUs, there are more specific rules which will create additional labels for GPU family, product and device count. For example, Flex 170:
@@ -27,6 +27,8 @@ gpu.intel.com/product=Max_1550
 
 Current covered platforms/devices are: Flex 140, Flex 170, Max 1100 and Max 1550.
 
+To identify other GPUs, see the graphics processor table [here](https://dgpu-docs.intel.com/devices/hardware-table.html#graphics-processor-table).
+
 ## GPU Plugin and NFD hook
 
 In GPU plugin, these labels are only applied when [Resource Management](README.md#fractional-resources-details) is enabled. With the NFD hook, labels are created regardless of how GPU plugin is configured.