search FAQ & notice: Howard's changes

Author: rlxdev

src/assets/data/NotificationBanner.json

@@ -9,16 +9,21 @@
     },
     {
       "contentType": "paragraph",
-      "content": "Keyword searching of CVE Records is now available in the search box above. Keywords may include a CVE ID (e.g., CVE-2024-1234), or one or more keywords separated by a space (e.g., authorization, SQL Injection, cross site scripting, etc.). Learn more "
+      "content": "Expanded keyword searching of CVE Records"
     },
     {
       "contentType": "internalLink",
-      "link": "/Media/News/item/blog/2024/12/11/CVE-List-Keyword-Search-Now-Available",
-      "linkText": "here"
+      "link": "/ResourcesSupport/FAQs#pc_cve_list_basicssearch_cve",
+      "linkText": "(with limitations)"
     },
     {
       "contentType": "paragraph",
-      "content": "."
+      "content": "is now available in the search box above. Text may include a CVE/CWE/CAPEC ID (e.g., CVE-2024-1234), or one or more keywords (e.g., 'SQL Injection', 'man-in-the-middle', etc.). Learn more"
+    },
+    {
+      "contentType": "internalLink",
+      "link": "/Media/News/item/blog/2024/12/11/CVE-List-Keyword-Search-Now-Available",
+      "linkText": "here."
     }
   ]
 }

src/assets/data/faqs.json

@@ -272,7 +272,7 @@
 				"questionText": "How do I search the CVE List",
 				"questionResponseParagraphs": [
 					"<b><i>Search Tips<i></b>",
-					"<ul><li>By Specific CVE ID<ul><li>Must include only one CVE ID per search.</li><li>CVE ID must include all letters, numbers, and hyphens associated with the CVE ID, e.g., CVE-2024-12345678.</li><li>“CVE” may be entered as “cve”, “CVE”, or as a combination of uppercase and lowercase, as casing is ignored during search.</li></ul></li><li>Multiple CVE IDs<ul><li>If you provide multiple CVE IDs, the search will only return results that refer to every CVE ID you specify, which may not be what you expect.</li><li>You may enter partial CVE IDs, for example <pre>cve-2022 cve-2024</pre> that will look for records referring to CVE IDs for BOTH years, which may yield better results than specifying complete CVE IDs.</li></ul></li><li>By other keyword(s)<ul><li>May contain words of alphanumeric and Unicode characters, as well as certain symbols (i.e., punctuation).<li>Must not contain any of the following symbols:<pre>() {} [] \" ' ` <> | ; ! ~ ^ * + %</pre></li></li><li>May contain one or more keywords, separated by a space.</li><li>Keywords may be entered in lowercase, uppercase, or a combination of both. Casing is ignored during search, e.g., Vulnerabilities, vulnerabilities, VULNERABILITIES.</li></ul></li></ul>"
+					"<p>You can now search using:</p><ul><li>IDs<ul><li>CVE ID<ul><li>specific CVE ID (e.g., \"CVE-2015-8405\")<ul><li>note that this returns records where there is a match for the CVE ID anywhere in the CVE record (e.g., \"CVE-2015-8405\" returns the CVE named, as well as any CVEs that has that CVE ID in the description)</ul><li>the nominal CVE ID Year - (e.g., \"CVE-2025\" returns all CVEs reserved in the CVE-2025 year series)<ul><li>note that the year must be a full year (e.g., \"CVE-202\" is invalid and will produce no results)</ul></ul><li>CWE ID - for specific Common Weakness Enumerations (e.g., \"CWE-123\")<li>CAPEC ID - for specific Common Attack Pattern Enumerations and Classifications (e.g., \"CAPEC-123\")</ul><li>General<ul><li>search terms may contain words of alphanumeric and Unicode characters, as well as certain symbols (i.e., punctuation).  The list of symbols currently not supported are: () {} [] \" ' ` <> | ; ! ~ ^ * + %<li>case-insensitive - (e.g., \"cwe-123\" and \"CWE-123\" returns the same results)<li>hyphenated words (e.g., \"man-in-the-middle\")<li>exact version strings (e.g., \"6.17.4\")<li>exact IPv4 strings (e.g., \"127.0.0.1\")<li>exact filenames (e.g., \"main.cpp\")<li>URLs (e.g., \"http://www.ibm.com/support/docview.wss?uid\")<li>combination of any of the above - separating terms with a space, you can search for any CVEs that contains ALL the search terms in its record (e.g., \"apache cwe-502 cve-2025\" will return all CVEs each of which containing all 3 terms)<ul><li>note that if you provide multiple CVE IDs, the search will only return results that contains ALL CVE IDs you specify in each record, which may not be what you expect.</ul><li>search terms are currently done using an exact match, so a full capability to match substrings is not available, (e.g., a search for \"cern\" will not return any records containing \"concern\"). However, a substring may sometimes be matched if a CVE Record contains a non-alphanumeric character immediately after the substring (e.g., if you want to search for a product using a CPE code, a search for \"cpe:2.3:a:gitlab:*\" will not produce any results at this time.  Instead, a search for \"cpe 2.3 a gitlab\" (i.e., the CPE string without the colon or asterisks) will return all CVEs that has \"cpe\", \"2.3\", and \"gitlab\" in all its fields).</ul></ul>"
 				]
 			},
 			{

src/components/NotificationBannerModule.vue

@@ -45,7 +45,7 @@
                     </span>
                     <div>
                       <span style="padding-left: 5px" v-for="(section, index) in notificationContents" :key="index">
-                        <span v-if="section.contentType == 'paragraph'" v-html="section.content + ' '"></span>
+                        <span v-if="section.contentType == 'paragraph'" v-html="section.content"></span>
                         <span class="has-text-weight-bold" v-if="section.contentType == 'bold'">{{section.content}} </span>
                         <a v-if="section.contentType == 'externalLink'" :href="section.link" target="_blank">{{section.linkText}}
                           <span class="icon cve-icon-xxs">