Fix Criteria defs in next.json

Last year we adjusted the definitions of the tools and clients Criteria
to make them focus on usage by software external to the OpenStack
community and internal to the OpenStack community respectively [1].
However, the definitions in the next.json document still reflect the
old, outdated definitions.  This patch sets that to rights by adjusting
the definitions in the next.json document to reflect the current state
of affairs.

Note: I considered just removing the definitions here entirely, but
it seems logical to keep them since the definitions in the CoreCriteria
document can and do change over time (so it's nice to know how the
Criteria were defined at the time the Guideline you're looking at
was approved).

[1] https://review.openstack.org/#/c/226978/

Change-Id: I57af817659a0d66a9d6c3c0d33e92e329033d5b5

next.json

@@ -3144,7 +3144,7 @@
         "weight": 6
     },
     "clients": {
-        "Description": "Candidates are widely used capabilities: Should be included if part of common libraries (Fog, Apache jclouds, etc)",
+        "Description": "Candidates are widely used capabilities: Should be included if called by common OpenStack clients (openstackclient, neutronclient, novaclient, etc) if necessary.  This Criteria pertains mostly to API versioning.  For example: if v2 of a given API is not used by other OpenStack clients but v1 is, then v2 doesn't achieve the 'used by clients' Criteria.",
         "name": "Used by Clients",
         "weight": 10
     },
@@ -3194,7 +3194,7 @@
         "weight": 9
     },
     "tools": {
-        "Description": "Candidates are widely used capabilities:Should be included if supported by common tools (RightScale, Scalr, CloudForms, ...)",
+        "Description": "Candidates are widely used capabilities: Should be included if supported by common tools outside of the OpenStack community (RightScale, Scalr, CloudForms, jClouds, Fog, etc...)",
         "name": "Used by Tools",
         "weight": 6
     }