ID 470465 - The "disable blink cache" preference has a misleading name and tooltip

Problem summary
The "disable blink cache" preference has a misleading name and tooltip. 

The documentation describes the preference as doing the following:

When enabled, nodes that support GPU caching pass on the GPU data to the last node that supports GPU caching and then transfer all the data back to the CPU at once.

In order to enable blink caching, the preference needs to be disabled which is potentially confusing.

Customer reported version
N/A

Customer reported platform

N/A

Steps to reproduce

1) The preference can be found by navigating tp Edit > Preferences > Performance > Hardware

2) The description for what this preference does can be found in the Preferences page of the Nuke documentation.

Expected behaviour
It would be clearer if the preference was named "enable blink cache", which is enabled by default.

Actual behaviour
The preference is named "disable blink cache", which is disabled by default.

Workaround
N/A

Reproduced by support

This bug has been reproduced in:
Nuke 12.2v5 - Windows 10

Nuke 12.1v1 - Windows 10

Earliest version tested
Nuke 12.1v1

- The preference has been named this way, and behaved in the same way, since it was implemented.