Merge pull request #573 from tigergraph/DOC-2349-remove-old-vers-3.6

DOC-2349-remove-old-vers-3.6

modules/data-definition/pages/README.adoc

@@ -11,7 +11,7 @@ A graph schema is a "dictionary" that defines the types of entities, vertices an
 Each vertex or edge type has a name and a set of attributes (properties) associated with it.
 For example, a `Book` vertex could have title, author, publication year, genre, and language attributes.
 
-To learn about the GSQL commands used to define a schema, see xref:3.2@gsql-ref:ddl-and-loading:defining-a-graph-schema.adoc[GSQL language reference: Defining a Graph Schema.]
+To learn about the GSQL commands used to define a schema, see xref:gsql-ref:ddl-and-loading:defining-a-graph-schema.adoc[GSQL language reference: Defining a Graph Schema.]
 
 == Modify a schema
 After you define a graph schema, you can still modify it. This includes but is not limited to:
@@ -25,7 +25,7 @@ Data already stored in the graph and which is not logically part of the change w
 For example, if you had 100 Book vertices and then added an attribute to the Book schema, you would still have 100 Books, with default values for the new attribute.
 If you dropped a Book attribute, you still would have all your books, but the one attribute would be gone.
 
-To learn about the GSQL commands used in modifying a schema, see xref:3.2@gsql-ref:ddl-and-loading:modifying-a-graph-schema.adoc[GSQL language reference: Modifying a Graph Schema.]
+To learn about the GSQL commands used in modifying a schema, see xref:gsql-ref:ddl-and-loading:modifying-a-graph-schema.adoc[GSQL language reference: Modifying a Graph Schema.]
 
 == Reset all
 You can clear the entire graph data store and erase all related definitions, including graph schema, loading jobs, queries as well as users and roles.

modules/release-notes/pages/index.adoc

@@ -230,10 +230,10 @@ If the `primary_id_as_attribute` option is selected, then attending to perform n
 * For a list of known issues for GraphStudio and Admin Portal, please see xref:{page-component-version}@gui:graphstudio:known-issues.adoc[Known issues for GraphStudio] and xref:{page-component-version}@gui:admin-portal:known-issues.adoc[Known issues for Admin Portal].
 
 == Release notes for previous versions
-* xref:3.5@tigergraph-server:release-notes:index.adoc[Release notes - TigerGraph 3.5]
-* xref:3.4@tigergraph-server:release-notes:release-notes.adoc[Release notes - TigerGraph 3.4]
-* xref:3.3@tigergraph-server:release-notes:release-notes.adoc[Release notes - TigerGraph 3.3]
-* xref:3.2@tigergraph-server:release-notes:release-notes.adoc[Release notes - TigerGraph 3.2]
+* xref:attachment$Release_Notes_3.5.pdf[Release notes - TigerGraph 3.5]
+* xref:attachment$Release_Notes_3.4.pdf[Release notes - TigerGraph 3.4]
+* xref:attachment$Release_Notes_3.3.pdf[Release notes - TigerGraph 3.3]
+* xref:attachment$Release_Notes_3.2.pdf[Release notes - TigerGraph 3.2]
 
 == Compatibility with TigerGraph 3.4
 * A single `POST-ACCUM` clause can no longer reference more than one vertex alias in Syntax V1.

modules/user-access/pages/vlac.adoc

@@ -64,7 +64,7 @@ Features not yet supported:
 In summary, all necessary operations to set up VLAC graphs and users are supported in GSQL. Due to a known bug, standard users (with `querywriter` and `queryreader` roles) can run some DDL operations which they should not be able to.
 ====
 
-We'll use the graph xref:3.2@gsql-ref:querying:appendix-query/example-graphs.adoc#_socialnet[socialNet] as an example in the following sections.
+We'll use the graph xref:gsql-ref:appendix:example-graphs.adoc#_social_net[socialNet] as an example in the following sections.
 
 == Tag Management
 
@@ -259,10 +259,10 @@ There are three main options for tagging vertices in the base graph.
 
 === Add tags on existing data
 
-In GSQL, special vertex methods are provided to access and modify the tags of a vertex in a DML query (full list available on page xref:3.2@gsql-ref:querying:func/vertex-methods.adoc[]).
+In GSQL, special vertex methods are provided to access and modify the tags of a vertex in a DML query (full list available on page xref:gsql-ref:querying:func/vertex-methods.adoc[]).
 These functions are only available for vertex aliases (defined in the `FROM` clause of a `SELECT` statement); they cannot be applied to vertex variables in other contexts.
 
-There are xref:3.2@gsql-ref:querying:func/vertex-methods.adoc[8 DML-level tag-access functions] in the vertex-query block or edge-query block. Use the xref:3.2@gsql-ref:querying:func/vertex-methods.adoc#_addtags[addTags()] function to tag a vertex.
+There are xref:qsql-ref:querying:func/vertex-methods.adoc[8 DML-level tag-access functions] in the vertex-query block or edge-query block. Use the xref:gsql-ref:querying:func/vertex-methods.adoc#_addtags[addTags()] function to tag a vertex.
 
 ==== Required privilege
 
@@ -301,7 +301,7 @@ CREATE QUERY addTagsToPerson() {
 }
 ----
 
-Use xref:3.2@gsql-ref:querying:func/vertex-methods.adoc#_removetags[] and xref:3.2@gsql-ref:querying:func/vertex-methods.adoc#_removealltags[] to remove tags from vertices:
+Use xref:gsql-ref:querying:func/vertex-methods.adoc#_removetags[] and xref:gsql-ref:querying:func/vertex-methods.adoc#_removealltags[] to remove tags from vertices:
 
 [source,gsql]
 ----