diff --git a/doc/administration/troubleshooting/elasticsearch.md b/doc/administration/troubleshooting/elasticsearch.md
index 6193d495d21b054ea23b4a4642006d2090c4fbac..85a0de506bfbd9870f6108cb861ef134c97dd52e 100644
--- a/doc/administration/troubleshooting/elasticsearch.md
+++ b/doc/administration/troubleshooting/elasticsearch.md
@@ -17,20 +17,6 @@ Troubleshooting Elasticsearch requires:
 - Knowledge of common terms.
 - Establishing within which category the problem fits.
 
-## Common terminology
-
-- **Lucene**: A full-text search library written in Java.
-- **Near real time (NRT)**: Refers to the slight latency from the time to index a
-  document to the time when it becomes searchable.
-- **Cluster**: A collection of one or more nodes that work together to hold all
-  the data, providing indexing and search capabilities.
-- **Node**: A single server that works as part of a cluster.
-- **Index**: A collection of documents that have somewhat similar characteristics.
-- **Document**: A basic unit of information that can be indexed.
-- **Shards**: Fully-functional and independent subdivisions of indices. Each shard is actually
-  a Lucene index.
-- **Replicas**: Failover mechanisms that duplicate indices.
-
 ## Troubleshooting workflows
 
 The type of problem will determine what steps to take. The possible troubleshooting workflows are for:
diff --git a/doc/integration/advanced_search/elasticsearch_troubleshooting.md b/doc/integration/advanced_search/elasticsearch_troubleshooting.md
index e061829deec352f0f1a7ef3e75c10cae116bb341..a07c0aef189e5f25802c742a4305d6b9b9c81246 100644
--- a/doc/integration/advanced_search/elasticsearch_troubleshooting.md
+++ b/doc/integration/advanced_search/elasticsearch_troubleshooting.md
@@ -24,6 +24,20 @@ integration are logs. The most relevant logs for this integration are:
 
 Here are some common pitfalls and how to overcome them.
 
+## Common terminology
+
+- **Lucene**: A full-text search library written in Java.
+- **Near real time (NRT)**: Refers to the slight latency from the time to index a
+  document to the time when it becomes searchable.
+- **Cluster**: A collection of one or more nodes that work together to hold all
+  the data, providing indexing and search capabilities.
+- **Node**: A single server that works as part of a cluster.
+- **Index**: A collection of documents that have somewhat similar characteristics.
+- **Document**: A basic unit of information that can be indexed.
+- **Shards**: Fully-functional and independent subdivisions of indices. Each shard is actually
+  a Lucene index.
+- **Replicas**: Failover mechanisms that duplicate indices.
+
 ## How can I verify that my GitLab instance is using Elasticsearch?
 
 There are a couple of ways to achieve that: