diff --git a/_field-types/supported-field-types/wildcard.md b/_field-types/supported-field-types/wildcard.md
index 0f8c1761354..1e4aacd39b0 100644
--- a/_field-types/supported-field-types/wildcard.md
+++ b/_field-types/supported-field-types/wildcard.md
@@ -22,6 +22,9 @@ At search time, required substrings from the query pattern are matched against t
 In general, exact match queries (like [`term`]({{site.url}}{{site.baseurl}}/query-dsl/term/term/) or [`terms`]({{site.url}}{{site.baseurl}}/query-dsl/term/term/) queries) perform less effectively on `wildcard` fields than on `keyword` fields, while [`wildcard`]({{site.url}}{{site.baseurl}}/query-dsl/term/wildcard/), [`prefix`]({{site.url}}{{site.baseurl}}/query-dsl/term/prefix/), and [`regexp`]({{site.url}}{{site.baseurl}}/query-dsl/term/regexp/) queries perform better on `wildcard` fields.
 {: .tip}
 
+Wildcard fields do not support highlighting.
+{: .note}
+
 ## Example
 
 Create a mapping with a `wildcard` field:
@@ -40,6 +43,9 @@ PUT logs
 ```
 {% include copy-curl.html %}
 
+All queries on wildcard fields have a constant score---usually `1`. You can override the constant score using the `boost` parameter.
+{: .note}
+
 ## Parameters
 
 The following table lists all parameters available for `wildcard` fields.