Minor issue with code for bug bounty

Regardless of whether a typo in a comment header is a bug or not (it isn't), this is amusing enough to dig into.

Here are the reasons why there should be no bounty paid on this minor issue, ranked by importance:

This typo is not in RaiBlocks code, but in the included OpenCL module. The referenced comment clearly states,

/*
 * Copyright (c) 2008-2015 The Khronos Group Inc. 
 [...]
 *   \brief C++ bindings for OpenCL 1.0 (rev 48), OpenCL 1.1 (rev 33) and 
 *       OpenCL 1.2 (rev 15)    
 *   \author Benedict R. Gaster, Laurent Morichetti and Lee Howes
*/

The bug bounty offer clearly states,

If you believe you have found a bug in RaiBlocks.

This 'bug' isn't in RaiBlocks. Submitter should contact the Khronos Group for claims on their bug bounty program.

The submitter did not follow correct protocol as described in the bug bounty offer:

Notify us that you have found a bug in the #bug_bounties channel on Discord at chat.raiblocks.net

The Core team will review the issue and if it is determined that the reported bug has merit, they will work with you to fix the bug and your bounty will be rewarded.

The submitter has leaked the crucial details of this bug -- namely, a missing 's' in the word 'descriptions' -- prior to contacting the core dev team and resolving it. The offer clearly states,

If the details of the bug leak ahead of the retrospective being published, whether accidentally or maliciously, the contract between RaiBlocks and the reporter is null-and-void and the bug bounty will not be rewarded.

Lastly, this is a typo in a comment.

I advise @Jackoclypse to follow the protocol very literally next time should he wish to claim a typo in a comment for a bug bounty.