Apply suggestions from code review

Co-authored-by: Lisa Cawley <[email protected]>
Co-authored-by: gchaps <[email protected]>

docs/user/alerting/alert-types.asciidoc

@@ -32,9 +32,9 @@ For domain-specific alerts, refer to the documentation for that app.
 
 [NOTE]
 ==============================================
-Some alert types are paid commercial features, while others are free.
+Some alert types are subscription features, while others are free features.
 For a comparison of the Elastic subscription levels,
-see https://www.elastic.co/subscriptions[the subscription page].
+see {subscriptions}[the subscription page].
 ==============================================
 
 

x-pack/plugins/alerts/README.md

@@ -129,11 +129,11 @@ For example, if the `context` has one variable `foo` which is an object that has
 
 ## Licensing
 
-Currently most of the alerts are licensed as "basic". But some alert types are at least "gold" level, eg tracking containment alert.
+Currently most of the alerts are free features. But some alert types are subscription features, such as the tracking containment alert.
 
 ## Documentation
 
-You should also create some asciidoc for the new alert type. An entry should be made in the alert type index - [`docs/user/alerting/alert-types.asciidoc`](../../../docs/user/alerting/alert-types.asciidoc) which points to a new document for the alert type that should be in the directory [`docs/user/alerting/alert-types`](../../../docs/user/alerting/alert-types).
+You should create documentation for the new alert type. Make an entry in the alert type index [`docs/user/alerting/alert-types.asciidoc`](../../../docs/user/alerting/alert-types.asciidoc) that points to a new document for the alert type that should be in the directory [`docs/user/alerting/alert-types`](../../../docs/user/alerting/alert-types).
 
 ## Tests