diff --git a/code/go/ecs/data_stream.go b/code/go/ecs/data_stream.go
index 44ca62920e..e641fbb514 100644
--- a/code/go/ecs/data_stream.go
+++ b/code/go/ecs/data_stream.go
@@ -22,7 +22,7 @@ package ecs
 // The data_stream fields take part in defining the new data stream naming
 // scheme.
 // In the new data stream naming scheme the value of the data stream fields
-// combine to the name of the actual data stream in the following manner
+// combine to the name of the actual data stream in the following manner:
 // `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`. This
 // means the fields can only contain characters that are valid as part of names
 // of data streams. More details about this can be found in this
diff --git a/docs/field-details.asciidoc b/docs/field-details.asciidoc
index 63aa2209e5..6eab9e7304 100644
--- a/docs/field-details.asciidoc
+++ b/docs/field-details.asciidoc
@@ -1022,7 +1022,7 @@ example: `docker`
 
 The data_stream fields take part in defining the new data stream naming scheme.
 
-In the new data stream naming scheme the value of the data stream fields combine to the name of the actual data stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`. This means the fields can only contain characters that are valid as part of names of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog post].
+In the new data stream naming scheme the value of the data stream fields combine to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`. This means the fields can only contain characters that are valid as part of names of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog post].
 
 An Elasticsearch data stream consists of one or more backing indices, and a data stream name forms part of the backing indices names. Due to this convention, data streams must also follow index naming restrictions. For example, data stream names cannot include `\`, `/`, `*`, `?`, `"`, `<`, `>`, `|`, ` ` (space character), `,`, or `#`. Please see the Elasticsearch reference for additional https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html#indices-create-api-path-params[restrictions].
 
diff --git a/experimental/generated/beats/fields.ecs.yml b/experimental/generated/beats/fields.ecs.yml
index 759334ed27..577e1c2a34 100644
--- a/experimental/generated/beats/fields.ecs.yml
+++ b/experimental/generated/beats/fields.ecs.yml
@@ -632,7 +632,7 @@
       naming scheme.
 
       In the new data stream naming scheme the value of the data stream fields combine
-      to the name of the actual data stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
+      to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
       This means the fields can only contain characters that are valid as part of
       names of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog
       post].
diff --git a/experimental/generated/ecs/ecs_nested.yml b/experimental/generated/ecs/ecs_nested.yml
index ad7709fbe8..27f4438255 100644
--- a/experimental/generated/ecs/ecs_nested.yml
+++ b/experimental/generated/ecs/ecs_nested.yml
@@ -1061,7 +1061,7 @@ data_stream:
     scheme.
 
     In the new data stream naming scheme the value of the data stream fields combine
-    to the name of the actual data stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
+    to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
     This means the fields can only contain characters that are valid as part of names
     of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog
     post].
diff --git a/generated/beats/fields.ecs.yml b/generated/beats/fields.ecs.yml
index 0cbc6d6722..cdc0c61991 100644
--- a/generated/beats/fields.ecs.yml
+++ b/generated/beats/fields.ecs.yml
@@ -641,7 +641,7 @@
       naming scheme.
 
       In the new data stream naming scheme the value of the data stream fields combine
-      to the name of the actual data stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
+      to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
       This means the fields can only contain characters that are valid as part of
       names of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog
       post].
diff --git a/generated/ecs/ecs_nested.yml b/generated/ecs/ecs_nested.yml
index 0952a796c2..98f8def9fe 100644
--- a/generated/ecs/ecs_nested.yml
+++ b/generated/ecs/ecs_nested.yml
@@ -1067,7 +1067,7 @@ data_stream:
     scheme.
 
     In the new data stream naming scheme the value of the data stream fields combine
-    to the name of the actual data stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
+    to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
     This means the fields can only contain characters that are valid as part of names
     of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog
     post].
diff --git a/schemas/data_stream.yml b/schemas/data_stream.yml
index d89726318d..de6f89ba45 100644
--- a/schemas/data_stream.yml
+++ b/schemas/data_stream.yml
@@ -6,7 +6,7 @@
     The data_stream fields take part in defining the new data stream naming scheme.
 
     In the new data stream naming scheme the value of the data stream fields combine to the name of the actual data
-    stream in the following manner `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`. This means the fields
+    stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`. This means the fields
     can only contain characters that are valid as part of names of data streams. More details about this can be found in
     this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog post].