Replaced EOL 7.1 with evergreen attribute

Author: RichardSmedley

modules/concept-docs/pages/analytics-for-sdk-users.adoc

@@ -21,5 +21,5 @@ For complex and long-running queries, involving large ad hoc join, set, aggregat
 
 == Additional Resources
 
-* Start with our  xref:7.1@server:analytics:primer-beer.adoc[introductory primer].
+* Start with our  xref:{version-server}@server:analytics:primer-beer.adoc[introductory primer].
 * Read the practical introduction xref:howtos:analytics-using-sdk.adoc[using analytics from the SDK].

modules/concept-docs/pages/collections.adoc

@@ -6,9 +6,9 @@
 [abstract]
 {description}
 
-The Collections feature in Couchbase Server is fully implemented in the 3.2 API version of the Couchbase SDK.
+The Collections feature in Couchbase Server is fully implemented in the 3.x API versions of the Couchbase SDK.
 
-Information on _Collections_ can be found in the xref:7.1@server:learn:data/scopes-and-collections.adoc[server docs].
+Information on _Collections_ can be found in the xref:{version-server}@server:learn:data/scopes-and-collections.adoc[server docs].
 
 == Using Collections & Scopes
 

modules/concept-docs/pages/compression.adoc

@@ -14,7 +14,7 @@ Documents may already be stored compressed with Snappy on the server.
 New documents may be passed from client applications to the server in compressed form, saving around 40% in bandwidth (depending on the document content and size), and also transmission time.
 These operations take place automatically, after the SDK negotiates the capability with the server, and do not require any changes on the client side.
 
-For SDKs with Snappy compression enabled, documents will be automatically compressed if the xref:7.1@server:learn:buckets-memory-and-storage/compression.adoc#compression-modes[Couchbase Server] is not set to `Off` for Compression see xref:#minimum-size[see below].
+For SDKs with Snappy compression enabled, documents will be automatically compressed if the xref:{version-server}@server:learn:buckets-memory-and-storage/compression.adoc#compression-modes[Couchbase Server] is not set to `Off` for Compression see xref:#minimum-size[see below].
 Instructions to disable compression can be found at xref:#threshold[the bottom of the page].
 
 == Limits

modules/concept-docs/pages/documents.adoc

@@ -57,7 +57,7 @@ If you wish to only modify certain parts of a document, you can use xref:subdocu
 include::devguide:example$java/DocumentsExample.java[tag=mutate-in]
 ----
 
-or xref:7.1@server:n1ql:n1ql-language-reference/update.adoc[N1QL UPDATE] to update documents based on specific query criteria:
+or xref:{version-server}@server:n1ql:n1ql-language-reference/update.adoc[N1QL UPDATE] to update documents based on specific query criteria:
 
 [source,sql]
 ----

modules/concept-docs/pages/n1ql-query.adoc

@@ -113,7 +113,7 @@ include::{version-common}@sdk:shared:partial$n1ql-queries.adoc[tag=index-consist
 
 The following options are available:
 
-include::7.1@server:learn:page$services-and-indexes/indexes/index-replication.adoc[tag=scan_consistency]
+include::{version-server}@server:learn:page$services-and-indexes/indexes/index-replication.adoc[tag=scan_consistency]
 
 Consider the following snippet:
 

modules/concept-docs/pages/querying-your-data.adoc

@@ -284,7 +284,7 @@ You can follow the links below for more information on the services with the Cou
 * xref:concept-docs:n1ql-query.adoc[Query Service]
 * xref:concept-docs:full-text-search-overview.adoc[Full Text Search]
 * xref:concept-docs:understanding-views.adoc[MapReduce Views]
-* xref:7.1@server:connectors:intro.adoc[Connectors]
+* xref:{version-server}@server:connectors:intro.adoc[Connectors]
 
 
 == Use Cases
@@ -299,7 +299,7 @@ If you know the path to the piece of information that you need within a JSON doc
 
 === Long Running Queries & Big Data
 
-xref:7.1@server:learn:services-and-indexes/services/analytics-service.adoc[Couchbase Analytics Service (CBAS)] performs well on huge datasets, with complex aggregations, and uses {sqlpp} for Analytics, which gives a similar query experience to {sqlpp} for Query.
+xref:{version-server}@server:learn:services-and-indexes/services/analytics-service.adoc[Couchbase Analytics Service (CBAS)] performs well on huge datasets, with complex aggregations, and uses {sqlpp} for Analytics, which gives a similar query experience to {sqlpp} for Query.
 CBAS supports workloads involving only SELECT (not INSERT or UPDATE), and uses local secondary indexes.
 Scalable performance comes from multi-node partitioned-parallel join, sort, aggregate, and grouped aggregate operators, and multiple storage devices (vbuckets over several nodes).
 
@@ -342,10 +342,10 @@ Use the Full Text Search (FTS) service when you want to take advantage of natura
 For phrase matching, over free-form text, or matching over word stems, FTS is a powerful solution.
 
 There are more concepts to learn, as FTS offers a very flexible service.
-In particular, care should be taken over building indexes, to stop them becoming unnecessarily large -- see our xref:7.1@server:fts:full-text-intro.adoc[FTS documentation].
+In particular, care should be taken over building indexes, to stop them becoming unnecessarily large -- see our xref:{version-server}@server:fts:full-text-intro.adoc[FTS documentation].
 Once again, the SDK abstracts away much of the complexity from deeply nested queries, and the interface is similar to our Query Service.
 
-From Couchbase Server 6.5, xref:7.1@server:n1ql:n1ql-language-reference/searchfun.adoc[Search Functions] allow the use of FTS _within_ {sqlpp} queries.
+From Couchbase Server 6.5, xref:{version-server}@server:n1ql:n1ql-language-reference/searchfun.adoc[Search Functions] allow the use of FTS _within_ {sqlpp} queries.
 
 
 === Querying

modules/howtos/pages/analytics-using-sdk.adoc

@@ -19,7 +19,7 @@ or the Enterprise Edition of self-managed Couchbase Server.
 
 == Getting Started
 
-After familiarizing yourself with our xref:7.1@server:analytics:primer-beer.adoc[introductory primer],
+After familiarizing yourself with our xref:{version-server}@server:analytics:primer-beer.adoc[introductory primer],
 in particular creating a dataset and linking it to a bucket, try Couchbase Analytics using the Java SDK.
 Intentionally, the API for analytics is nearly identical to that of the query service.
 

modules/howtos/pages/kv-operations.adoc

@@ -309,7 +309,7 @@ include::{version-common}@sdk:shared:partial$atomic.adoc[tag=xdcr]
 
 == Scoped KV Operations
 
-It is possible to perform scoped key-value operations on named xref:7.1@server:learn:data/scopes-and-collections.adoc[`Collections`] _with Couchbase Server release 7.x_.
+It is possible to perform scoped key-value operations on named xref:{version-server}@server:learn:data/scopes-and-collections.adoc[`Collections`] _with Couchbase Server release 7.x_.
 See the https://docs.couchbase.com/sdk-api/couchbase-java-client/com/couchbase/client/java/Collection.html[API docs] for more information.
 
 Here is an example showing an upsert in the `users` collection, which lives in the `travel-sample.tenant_agent_00` keyspace:

modules/howtos/pages/sqlpp-queries-with-sdk.adoc

@@ -262,7 +262,7 @@ NOTE: {sqlpp} is not the only query option in Couchbase.
 Be sure to check that xref:concept-docs:data-services.adoc[your use case fits your selection of query service].
 
 * For a deeper dive into {sqlpp} from the SDK, refer to our xref:concept-docs:n1ql-query.adoc[{sqlpp} SDK concept doc].
-* The xref:7.1@server:n1ql:n1ql-language-reference/index.adoc[Server doc {sqlpp} intro] introduces a complete guide to the {sqlpp} language, including all of the latest additions.
+* The xref:{version-server}@server:n1ql:n1ql-language-reference/index.adoc[Server doc {sqlpp} intro] introduces a complete guide to the {sqlpp} language, including all of the latest additions.
 * The http://query.pub.couchbase.com/tutorial/#1[{sqlpp} interactive tutorial] is a good introduction to the basics of {sqlpp} use.
-* For scaling up queries, be sure to xref:7.1@server:learn:services-and-indexes/indexes/index-replication.adoc[read up on Indexes].
+* For scaling up queries, be sure to xref:{version-server}@server:learn:services-and-indexes/indexes/index-replication.adoc[read up on Indexes].
 * Read more on xref:concept-docs:http-services.adoc#long-running-queries-big-data[when to choose the Analytics service].

modules/project-docs/pages/distributed-acid-transactions-migration-guide.adoc

@@ -12,7 +12,7 @@ We subsequently chose to integrate transactions directly into the SDKs with the
 
 This document details the small changes that existing users of the legacy transactions library need to make, to migrate to the SDK-integrated version.
 
-The xref:3.2@java-sdk:project-docs:distributed-transactions-java-release-notes.adoc[legacy transactions library] will continue to be supported with bugfixes for some time, but new transaction features will only be added to the SDK and it is recommended that all users migrate.
+The https://docs-archive.couchbase.com/java-sdk/3.2/project-docs/distributed-transactions-java-release-notes.html[legacy transactions library] will continue to be supported with bugfixes for some time, but new transaction features will only be added to the SDK and it is recommended that all users migrate.
 
 == Accessing transactions
 
@@ -184,5 +184,5 @@ include::devguide:example$java/TransactionsMigration.java[tag=log,indent=0]
 
 == Further Reading
 
-* There's plenty of explanation about how Transactions work in Couchbase in our xref:7.1@server:learn:data/transactions.adoc[Transactions documentation].
+* There's plenty of explanation about how Transactions work in Couchbase in our xref:{version-server}@server:learn:data/transactions.adoc[Transactions documentation].
 * The xref:howtos:distributed-acid-transactions-from-the-sdk.adoc[Java SDK transactions documentation].