diff --git a/data-streams.asciidoc b/data-streams.asciidoc
index ef51546ac6..1333d9d5e3 100644
--- a/data-streams.asciidoc
+++ b/data-streams.asciidoc
@@ -39,7 +39,8 @@ and another dataset for disk I/O metrics with a field describing the number of b
 A user-configurable arbitrary grouping, such as an environment (`dev`, `prod`, or `qa`),
 a team, or a strategic business unit.
 A `namespace` can be up to 100 bytes in length (multibyte characters will count toward this limit faster).
-Using a namespace makes it easier to search the data from a given source by using index patterns, or to give users permissions to data by assigning an index pattern to user roles.
+Using a namespace makes it easier to search data from a given source by using a matching pattern.
+You can also use matching patterns to give users access to data when creating user roles.
 // Corresponds to the `data_stream.dataset` field.
 
 The naming scheme separates each components with a `-` character:
@@ -76,10 +77,10 @@ Under the hood though, things are a bit more complex.
 All of the juicy details are available in {ref}/data-streams.html[{es} Data streams].
 
 [discrete]
-[[data-streams-index-pattern]]
-== Index patterns
+[[data-streams-data-view]]
+== {data-sources-cap}
 
-When searching your data in {kib}, you can use an {kibana-ref}/index-patterns.html[index pattern]
+When searching your data in {kib}, you can use a {kibana-ref}/data-views.html[{data-source}]
 to search across all or some of your data streams.
 
 [discrete]