minor edits

.github/vale-styles/Yugabyte/spelling-exceptions.txt

@@ -59,6 +59,7 @@ backport
 backported
 backporting
 backports
+backquote
 backtrace
 backtraced
 backtraces
@@ -138,6 +139,7 @@ crosslinked
 crosslinking
 crosslinks
 Crossplane
+crosstab
 CrowdIn
 CSV
 Cutover
@@ -878,6 +880,8 @@ YBase
 ycqlsh
 YouTrack
 ysqlsh
+ysql_dump
+ysql_dumpall
 ytt
 Yubico
 Yugabyte

docs/content/preview/architecture/transactions/concurrency-control.md

@@ -300,7 +300,7 @@ commit;
 
 ### Best-effort internal retries for first statement in a transaction
 
-Note that we see the error message `All transparent retries exhausted` in the preceding example because if the transaction T1, when executing the first statement, finds another concurrent conflicting transaction with equal or higher priority, then T1 will perform a few retries with exponential backoff before giving up in anticipation that the other transaction will be done in some time. The number of retries are configurable by the `yb_max_query_layer_retries` session variable and the exponential backoff parameters are the same as the ones described in [Performance tuning](../read-committed/#performance-tuning).
+Note that we see the error message `All transparent retries exhausted` in the preceding example because if the transaction T1, when executing the first statement, finds another concurrent conflicting transaction with equal or higher priority, then T1 will perform a few retries with exponential backoff before giving up in anticipation that the other transaction will be done in some time. The number of retries are configurable by the `yb_max_query_layer_retries` YSQL configuration parameter and the exponential backoff parameters are the same as the ones described in [Performance tuning](../read-committed/#performance-tuning).
 
 Each retry will use a newer snapshot of the database in anticipation that the conflicts might not occur. This is done because if the read time of the new snapshot is higher than the commit time of the earlier conflicting transaction T2, the conflicts with T2 would essentially be voided as T1 and T2 would no longer be "concurrent".
 

docs/content/preview/contribute/docs/all-page-elements.md

@@ -91,7 +91,7 @@ To build and run the application, do the following:
 
     The application needs to establish a connection to the YugabyteDB cluster. To do this:
 
-    - Set the following configuration parameters:
+    - Set the following connection parameters:
 
         - **host** - the host name of your YugabyteDB cluster. To obtain a YugabyteDB Managed cluster host name, sign in to YugabyteDB Managed, select your cluster on the **Clusters** page, and click **Settings**. The host is displayed under **Connection Parameters**.
         - **port** - the port number that will be used by the JDBC driver (the default YugabyteDB YSQL port is 5433).