Merge branch 'main' into dev

Author: samzhou2

modules/savanna/modules/graph-development/pages/gsql-editor/how2-edit-gsql-query.adoc

@@ -22,7 +22,7 @@ image::Screenshot 2024-04-18 at 10.12.15 AM.png[]
 The opened files will be listed on the top tabs on the code edit folder
 +
 image::query-editor.png[]
-+
+
 
 == Run GSQL Query
 

modules/savanna/modules/overview/pages/pricing.adoc

@@ -1,6 +1,7 @@
 = Pricing
 
-TigerGraph Savanna offers a flexible and transparent pricing model designed to accommodate a wide range of usage scenarios, from small-scale projects to large enterprise deployments. Our pricing structure is crafted to provide you with the best value while ensuring your graph database solutions are scalable, reliable, and high-performing.
+TigerGraph Savanna offers a flexible and transparent pricing model designed to accommodate a wide range of usage scenarios, from small-scale projects to large enterprise deployments.
+Our pricing structure is crafted to provide you with the best value while ensuring your graph database solutions are scalable, reliable, and high-performing.
 
 == Select Platform and Region
 :provider: AWS
@@ -43,7 +44,8 @@ Compute resources on TigerGraph Savanna are billed based on the number of TCRs c
 
 === TigerGraph Credits
 
-A TigerGraph Credit (TCR) is a unit that represents the cost of using compute resources on TigerGraph Savanna. By using TCRs, you can easily scale your compute resources up or down to meet your performance needs without worrying about complex pricing structures.
+A TigerGraph Credit (TCR) is a unit that represents the cost of using compute resources on TigerGraph Savanna.
+By using TCRs, you can easily scale your compute resources up or down to meet your performance needs without worrying about complex pricing structures.
 
 The exchange rate for TigerGraph Credits is straightforward:
 
@@ -55,7 +57,14 @@ This means that for every TigerGraph Credit you consume, you will be billed $4.0
 === Compute Pricing Table
 
 The following table outlines the cost in TCRs for different sizes of compute resources.
-The compute costs are distinct from the storage fees listed below and are metered based on actual usage. For inquiries about pricing, volume discounts, or deploying in other regions, please contact us at sales@tigergraph.com.
+The compute costs are distinct from the storage fees listed below and are metered based on actual usage.
+For inquiries about pricing, volume discounts, or deploying in other regions, please contact us at sales@tigergraph.com.
+
+[NOTE]
+====
+Prices depend on your region.
+The table automatically adjusts to the region you select above.
+====
 
 ++++
 
@@ -168,7 +177,7 @@ High Availability (HA) on TigerGraph Savanna ensures your graph database remains
 
 [cols="3", separator=¦ ]
 |===
-¦ Compute Size ¦ Replica Factor ¦ Cost Mutiplier
+¦ Compute Size ¦ Replica Factor ¦ Cost Multiplier
 ¦ Sizes equal or below TG-8 ¦ 3 ¦ 2.8x
 ¦ Sizes above TG-8 ¦ 2 ¦ 1.95x 
 

modules/savanna/modules/resources/pages/faqs.adoc

@@ -132,7 +132,7 @@ A: The TigerGraph Savanna portal provides a browser-based interface that makes i
 
 A: TigerGraph uses GSQL, the query language designed for fast and scalable graph operations and analytics. GSQL's similarity to SQL, high-level syntax, Turing completeness, and built-in parallelism brings faster performance, faster development and the ability to describe any algorithm.
 
-You can start learning GSQL from our link:https://github.com/tigergraph/ecosys/blob/master/demos/guru_scripts/docker/tutorial/4.x/README.md[GSQL V3 Tutorial]. We also support a RESTful API and JSON output for easy integration with application languages like Python, Java, and C{pp}.
+You can start learning GSQL from our link:https://github.com/tigergraph/ecosys/blob/master/tutorials/GSQL.md[GSQL V3 Tutorial]. We also support a RESTful API and JSON output for easy integration with application languages like Python, Java, and C{pp}.
 
 Start learning GSQL and become a TigerGraph Certified Associate today with our link:https://www.tigergraph.com/certification/[Certification Program].
 

modules/savanna/modules/workgroup-workspace/pages/workspaces/readwrite-readonly.adoc

@@ -24,6 +24,37 @@ Read-only workspaces provide improved performance and scalability for read opera
 Current RO workspace requires manual sync up with the RW workspace to catch up with the latest change.
 ====
 
+=== Operations prohibited in a Read-Only (RO) Workspace
+
+Read-Only (RO) workspaces are optimized for read-intensive tasks and do not allow any operations that modify data or schemas. The following operations are strictly prohibited:
+
+.Database Operations
+- Running "gsql --reset" command.
+- Clearing the graph store.
+- Executing the DROP ALL command.
+
+.Schema Management
+- Updating schemas, including adding, updating, or dropping schema elements.
+- Creating, dropping, or running schema change jobs.
+
+.Graph Management
+- Creating or dropping graphs.
+- Exporting or importing database data.
+
+.Data Modification
+- Running any queries that modify the database data.
+- Inserting, updating, or deleting data.
+- Committing the data(such as new vertices or edges) in memory to disk. for example: rebuildnow operation
+
+.Loading Jobs
+- Creating, deleting, or running loading jobs.
+- Creating, deleting, pausing, restarting, or resuming connectors.
+- Creating or updating data sources.
+
+.Backup and Restore
+- Performing backup or restore operations.
+
+
 === Update Read-Only(RO) Workspace
 
 Once a Read-Only (RO) workspace is created, it also creates a snapshot of the data.

modules/savanna/modules/workgroup-workspace/pages/workspaces/workspace.adoc

@@ -25,6 +25,38 @@ It holds the persistent data that is loaded into TigerGraph and is accessible fo
 We only support a maximum of one Read-Write workspace to connect to a database.
 ====
 
+
+=== Operations prohibited in a Read-Only (RO) Workspace
+
+Read-Only (RO) workspaces are optimized for read-intensive tasks and do not allow any operations that modify data or schemas. The following operations are strictly prohibited:
+
+.Database Operations
+- Running "gsql --reset" command.
+- Clearing the graph store.
+- Executing the DROP ALL command.
+
+.Schema Management
+- Updating schemas, including adding, updating, or dropping schema elements.
+- Creating, dropping, or running schema change jobs.
+
+.Graph Management
+- Creating or dropping graphs.
+- Exporting or importing database data.
+
+.Data Modification
+- Running any queries that modify the database data.
+- Inserting, updating, or deleting data.
+- Committing the data(such as new vertices or edges) in memory to disk. for example: rebuildnow operation
+
+.Loading Jobs
+- Creating, deleting, or running loading jobs.
+- Creating, deleting, pausing, restarting, or resuming connectors.
+- Creating or updating data sources.
+
+.Backup and Restore
+- Performing backup or restore operations.
+
+
 == Next Steps
 See xref:workspaces/how2-create-a-workspace.adoc[] to get started.