Fix 8.13 bugs (#5002) (#5007)

* Remove screenshot of "Get started" page

* Emphasize that `is` doesn't support wildcards

(cherry picked from commit f0fafc8)

Co-authored-by: Joe Peeples <[email protected]>

docs/getting-started/security-ui.asciidoc

@@ -174,8 +174,6 @@ image::images/users/users-page.png[Users page]
 
 Quickly add security integrations that can ingest data and monitor your hosts.
 
-image::images/getting-started-pg.png[Get started page]
-
 [float]
 === Manage
 

docs/management/admin/trusted-apps.asciidoc

@@ -40,7 +40,7 @@ To add a trusted application:
 TIP: To find the signer's name for an application, go to *Kibana* -> *Discover* and query the process name of the application's executable (for example, `process.name : "mctray.exe"` for a McAfee security binary). Then, search the results for the `process.code_signature.subject_name` field, which contains the signer's name (for example, `McAfee, Inc.`).
 
 * `Operator`: Select an operator to define the condition:
-   ** `is`: Must be exactly equal to `Value`. This operation is required for the `Hash` and `Signature` field types.   
+   ** `is`: Must be _exactly_ equal to `Value`; wildcards are not supported. This operator is required for the `Hash` and `Signature` field types.
    ** `matches`: Can include wildcards in `Value`, such as `C:\path\*\app.exe`. This option is only available for the `Path` field type. Available wildcards are `?` (match one character) and `*` (match zero or more characters).
 
 * `Value`: Enter the hash value, file path, or signer name. To add an additional value, click *AND*.