Merge branch 'dev' into dynamic_tags

Author: JPryce-Aklundh

modules/ROOT/pages/appendix/gql-conformance/additional-cypher.adoc

@@ -1,4 +1,5 @@
 :description: Information about Cypher features not included in GQL.
+:test-skip: true
 = Additional Cypher features
 
 While the link:https://www.iso.org/standard/76120.html[GQL Standard] incorporates a lot of capabilities in Cypher, Cypher contains additional features that are not part of GQL and no GQL alternatives currently exist for them.
@@ -94,7 +95,7 @@ a|
 [source, cypher, role="noheader"]
 ----
 MATCH (n:$($label)),
-      ()-[r:$($type))]->()
+      ()-[r:$($type)]->()
 ----
 
 | xref:clauses/match.adoc#dynamic-match[`MATCH` nodes and relationships using dynamic node labels and relationship types]

modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc

@@ -40,7 +40,9 @@ In those cases, nothing needs to be specified and the `OPTIONS` map should be om
 [TIP]
 Creating an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege].
 
-A newly created index is not immediately available but is created in the background.
+[NOTE]
+An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
+To check the `state` of an index -- whether it is `ONLINE` (usable) or `POPULATING` (still being built; the `populationPercent` column shows the progress of the index creation) -- run the following command: `SHOW INDEXES`.
 
 [[create-range-index]]
 === Create a range index

modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc

@@ -3,7 +3,7 @@
 = Full-text indexes
 
 A full-text index is used to index nodes and relationships by `STRING` properties.
-Unlike xref:indexes/search-performance-indexes/managing-indexes.adoc#indexes-create-range-index[range] and xref:indexes/search-performance-indexes/managing-indexes.adoc#indexes-create-text-index[text] indexes, which can only perform limited `STRING` matching (exact, prefix, substring, or suffix matches), full-text indexes stores individual words in any given `STRING` property.
+Unlike xref:indexes/search-performance-indexes/managing-indexes.adoc#create-range-index[range] and xref:indexes/search-performance-indexes/managing-indexes.adoc#create-text-index[text] indexes, which can only perform limited `STRING` matching (exact, prefix, substring, or suffix matches), full-text indexes stores individual words in any given `STRING` property.
 This means that full-text indexes can be used to match within the _content_ of a `STRING` property.
 Full-text indexes also return a score of proximity between a given query string and the `STRING` values stored in the database, thus enabling them to semantically interpret data.
 
@@ -83,15 +83,15 @@ The default analyzer (`standard-no-stop-words`) analyzes both the indexed values
 Stop words are common words in a language that can be filtered out during 
 information retrieval tasks since they are considered to be of little use when determining the meaning of a string. These words are typically short and frequently used across various contexts. 
 
-For example, the following stop words are included in Lucene’s english analyzer: "a", "an", "and", "are", "as", "at", "be", "but”, and so on.
+For example, the following stop words are included in Lucene’s `english` analyzer: "a", "an", "and", "are", "as", "at", "be", "but", "by", "for", "if", "in", "into", "is", "it", "no", "not", "of", "on", "or", "such", "that", "the", "their", "then", "there", "these", "they", "this", "to", "was", "will", and "with".
 
 Removing stop words can help reduce the size of stored data and thereby improve the efficiency of data retrieval.
 ====
 
 In some cases, using different analyzers for the indexed values and query string is more appropriate.
-For example, if handling `STRING` values written in Swedish, it may be beneficial to select the _swedish_ analyzer, which knows how to tokenize Swedish words, and will avoid indexing Swedish stop words.
+For example, if handling `STRING` values written in Swedish, it may be beneficial to select the `swedish` analyzer, which knows how to tokenize Swedish words, and will avoid indexing Swedish stop words.
 
-A complete list of all available analyzers is included in the result of the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers`] procedure.
+The link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers()`] procedure shows all available analyzers.
 
 Neo4j also supports the use of custom analyzers.
 For more information, see the link:{neo4j-docs-base-uri}/java-reference/{page-version}/extending-neo4j/full-text-analyzer-provider[Java Reference Manual -> Full-text index analyzer providers].
@@ -134,13 +134,12 @@ For more information on how to configure full-text indexes, refer to the link:{n
 [[query-full-text-indexes]]
 == Query full-text indexes
 
+Unlike xref:indexes/search-performance-indexes/managing-indexes.adoc[search-performance indexes], full-text indexes are not automatically used by the xref:planning-and-tuning/execution-plans.adoc[Cypher query planner].
 To query a full-text index, use either the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_index_fulltext_querynodes[`db.index.fulltext.queryNodes`] or the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_index_fulltext_relationships[`db.index.fulltext.queryRelationships`] procedure.
 
 [NOTE]
-====
-Unlike other xref:indexes/search-performance-indexes/managing-indexes.adoc[search-performance indexes], full-text indexes are not automatically used by the xref:planning-and-tuning/execution-plans.adoc[Cypher query planner].
-To access full-text indexes, they must be explicitly called with the above-mentioned procedures.
-====
+An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
+To check the `state` of a full-text index -- whether it is `ONLINE` (usable) or `POPULATING` (still being built; the `populationPercent` column shows the progress of the index creation) -- run the following command: `SHOW FULLTEXT INDEXES`.
 
 This query uses the `db.index.fulltext.queryNodes` to look for `nils` in the previously created full-text index `namesAndTeams`:
 

modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc

@@ -196,6 +196,10 @@ Default value::: `100`
 
 To query a node vector index, use the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`] procedure.
 
+[NOTE]
+An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
+To check the `state` of a vector index -- whether it is `ONLINE` (usable) or `POPULATING` (still being built; the `populationPercent` column shows the progress of the index creation) -- run the following command: `SHOW VECTOR INDEXES`.
+
 .Signature for `db.index.vector.queryNodes`
 [source,syntax]
 ----