docs syntax highlighting improvements

Author: ibarrajo

docs/01-get-started/03-golang-hello-world.md

@@ -153,15 +153,15 @@ func helloWorldActivity(ctx context.Context, name string) (string, error) {
 
 Don't forget to register the workflow and activity to the worker.
 
-```Go
+```go
 func init() {
     workflow.Register(helloWorldWorkflow)
     activity.Register(helloWorldActivity)
 }
 ```
 
 Import the `context` module if it was not automatically added.
-```Go
+```go
 import (
     "context"
 )
@@ -176,7 +176,7 @@ cadence --domain test-domain workflow start --et 60 --tl test-worker --workflow_
 ```
 
 You should see logs in your worker terminal like
-```bash
+```log
 2023-07-16T11:30:02.717-0700    INFO    cadence-worker/code.go:104      Workflow completed. {"Domain": "test-domain", "TaskList": "test-worker", "WorkerID": "11294@uber-C02F18EQMD6R@test-worker@5829c68e-ace0-472f-b5f3-6ccfc7903dd5", "WorkflowType": "main.helloWorldWorkflow", "WorkflowID": "8acbda3c-d240-4f27-8388-97c866b8bfb5", "RunID": "4b91341f-056f-4f0b-ab64-83bcc3a53e5a", "Result": "Hello World!"}
 ```
 

docs/03-concepts/04-queries.md

@@ -19,7 +19,9 @@ Cadence team is currently working on implementing _update_ feature that would be
 The Cadence client libraries expose some predefined :query:queries: out of the box. Currently the only supported built-in :query: is _stack_trace_. This :query: returns stacks of all :workflow: owned threads. This is a great way to troubleshoot any :workflow: in production.
 
 Example
-```
-$cadence --do samples-domain wf query -w <workflowID> -qt __stack_trace
+<!-- TODO: enable wordWrap on this codeblock, at the moment its not yet supported. https://github.com/facebook/docusaurus/issues/7875 -->
+```sh wordWrap=true
+cadence --do samples-domain wf query -w <workflowID> -qt __stack_trace
+
 "coroutine 1 [blocked on selector-1.Select]:\nmain.sampleSignalCounterWorkflow(0x1a99ae8, 0xc00009d700, 0x0, 0x0, 0x0)\n\t/Users/qlong/indeed/cadence-samples/cmd/samples/recipes/signalcounter/signal_counter_workflow.go:38 +0x1be\nreflect.Value.call(0x1852ac0, 0x19cb608, 0x13, 0x1979180, 0x4, 0xc00045aa80, 0x2, 0x2, 0x2, 0x18, ...)\n\t/usr/local/Cellar/go/1.16.3/libexec/src/reflect/value.go:476 +0x8e7\nreflect.Value.Call(0x1852ac0, 0x19cb608, 0x13, 0xc00045aa80, 0x2, 0x2, 0x1, 0x2, 0xc00045a720)\n\t/usr/local/Cellar/go/1.16.3/libexec/src/reflect/value.go:337 +0xb9\ngo.uber.org/cadence/internal.(*workflowEnvironmentInterceptor).ExecuteWorkflow(0xc00045a720, 0x1a99ae8, 0xc00009d700, 0xc0001ca820, 0x20, 0xc00007fad0, 0x1, 0x1, 0x1, 0x1, ...)\n\t/Users/qlong/go/pkg/mod/go.uber.org/[email protected]/internal/workflow.go:372 +0x2cb\ngo.uber.org/cadence/internal.(*workflowExecutor).Execute(0xc000098d80, 0x1a99ae8, 0xc00009d700, 0xc0001b127e, 0x2, 0x2, 0xc00044cb01, 0xc000070101, 0xc000073738, 0x1729f25, ...)\n\t/Users/qlong/go/pkg/mod/go.uber.org/[email protected]/internal/internal_worker.go:699 +0x28d\ngo.uber.org/cadence/internal.(*syncWorkflowDefinition).Execute.func1(0x1a99ce0, 0xc00045a9f0)\n\t/Users/qlong/go/pkg/mod/go.uber.org/[email protected]/internal/internal_workflow.go:466 +0x106"
 ```

docs/03-concepts/10-http-api.md

@@ -25,7 +25,7 @@ To enable “start workflow” HTTP API, add `http` section to Cadence RPC confi
 services:
   frontend:
     rpc:
-      <...>
+      # ...
       http:
         port: 8800
         procedures:

docs/04-java-client/14-exception-handling.md

@@ -16,7 +16,7 @@ Exceptions thrown by a workflow are received by a workflow client wrapped into `
  In this [example](https://github.com/cadence-workflow/cadence-java-samples/blob/master/src/main/java/com/uber/cadence/samples/hello/HelloException.java) a Workflow Client executes a workflow which executes a child workflow which
  executes an activity which throws an IOException. The resulting exception stack trace is:
 
-```
+```log
  com.uber.cadence.client.WorkflowFailureException: WorkflowType="GreetingWorkflow::getGreeting", WorkflowID="38b9ce7a-e370-4cd8-a9f3-35e7295f7b3d", RunID="37ceb58c-9271-4fca-b5aa-ba06c5495214
      at com.uber.cadence.internal.dispatcher.UntypedWorkflowStubImpl.getResult(UntypedWorkflowStubImpl.java:139)
      at com.uber.cadence.internal.dispatcher.UntypedWorkflowStubImpl.getResult(UntypedWorkflowStubImpl.java:111)

docs/04-java-client/index.md

@@ -17,7 +17,7 @@ The following are important links for the Cadence Java client:
 
 Add *cadence-client* as a dependency to your *pom.xml*:
 
-```
+```xml
     <dependency>
       <groupId>com.uber.cadence</groupId>
       <artifactId>cadence-client</artifactId>
@@ -27,15 +27,15 @@ Add *cadence-client* as a dependency to your *pom.xml*:
 
 or to *build.gradle*:
 
-```
+```gradle
     dependencies {
       implementation group: 'com.uber.cadence', name: 'cadence-client', version: 'LATEST.RELEASE.VERSION'
     }
 ```
 
 If you are using [gradle 6.9 or older](https://docs.gradle.org/current/userguide/upgrading_version_6.html#sec:configuration_removal), you can use `compile group`
 
-```
+```gradle
     dependencies {
       compile group: 'com.uber.cadence', name: 'cadence-client', version: 'LATEST.RELEASE.VERSION'
     }

docs/05-go-client/18-workflow-replay-shadowing.md

@@ -52,7 +52,7 @@ replayer.RegisterWorkflow(myWorkflowFunc2, workflow.RegisterOptions{
 
 Replayer can read workflow history from a local json file or fetch it directly from the Cadence server. If you would like to use the first method, you can use the following CLI command, otherwise you can skip to the next step.
 
-```
+```bash
 cadence --do <domain> workflow show --wid <workflowID> --rid <runID> --of <output file name>
 ```
 

docs/06-cli/index.md

@@ -13,12 +13,12 @@ The Cadence :CLI: is a command-line tool you can use to perform various :task:ta
 ## Using the CLI
 
 ### Homebrew
-```
+```bash
 brew install cadence-workflow
 ```
 
 After the installation is done, you can use CLI:
-```
+```bash
 cadence --help
 ```
 This will always install the latest version. Follow [this instructions](https://github.com/cadence-workflow/cadence/discussions/4457) if you need to install older versions of Cadence CLI.
@@ -49,7 +49,7 @@ docker run -it --rm ubercadence/cli:master --address host.docker.internal:7933 -
 NOTE: Be sure to update your image when you want to try new features: `docker pull ubercadence/cli:master `
 
 NOTE: If you are running docker-compose Cadence server, you can also logon to the container to execute CLI:
-```
+```bash
 docker exec -it docker_cadence_1 /bin/bash
 
 # cadence --address $(hostname -i):7933 --do samples domain register
@@ -68,8 +68,8 @@ Alternatively, you can build the CLI image, see [instructions](https://github.co
 ## Documentation
 CLI are documented by `--help` or `-h` in ANY tab of all levels:
 
-```
-$cadence --help
+```sh-session
+$ cadence --help
 NAME:
    cadence - A command-line tool for cadence users
 
@@ -95,8 +95,8 @@ GLOBAL OPTIONS:
    --version, -v                        print the version
 ```
 And
-```
-$cadence workflow -h
+```sh-session
+$ cadence workflow -h
 NAME:
    cadence workflow - Operate cadence workflow
 
@@ -132,8 +132,8 @@ OPTIONS:
    --help, -h  show help
 ```
 
-```
-$cadence wf signal -h
+```sh-session
+$ cadence wf signal -h
 NAME:
    cadence workflow signal - signal a workflow execution