chore: Proofread entire Cadence-Docs repo (cadence-workflow#316)

* docs(community): proofread and fix spelling, grammar, and punctuation

- Fix capitalization: Github → GitHub, StackOverflow → Stack Overflow
- Fix spelling: fedback → feedback
- Fix punctuation: add missing periods, correct 'i.e.' usage
- Fix grammar: sentence fragments, awkward phrasing
- Remove duplicate H1 headers (title already in frontmatter)
- Update http → https links

Files changed:
- governance.mdx
- support.mdx
- how-to-contribute/getting-started.mdx
- how-to-contribute/pull-request-conventions.mdx
- how-to-contribute/ways-to-contribute.mdx

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs(glossary): fix spelling, grammar, and punctuation

- Fix spelling: correponding → corresponding, correspondent → corresponding
- Fix grammar: an decision → a decision, list of decision → list of decisions
- Remove double spaces and extra words
- Add missing periods at end of definitions
- Remove duplicate H1 header

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs(get-started): fix spelling, grammar, and punctuation

- Remove duplicate H1 headers (title already in frontmatter)
- Fix capitalization: cadence → Cadence, StackOverflow → Stack Overflow,
  Github → GitHub, Elastic Search → Elasticsearch
- Fix typos: HellowWorld → HelloWorld, for you → for your
- Fix grammar: which take → which takes, at background → in the background
- Add missing periods, remove double spaces

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs(use-cases): fix spelling, grammar, and punctuation

- Remove duplicate H1 headers (title already in frontmatter)
- Fix grammar: is also huge → is also a huge, correspondent → corresponding,
  as compared by → as compared to, which each → with each
- Fix typos: Half a a minute → Half a minute, overgenous → overgenerous
- Add Oxford comma, remove trailing colon from link text

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs: proofread docs/03-concepts/ folder

- Remove H1 headers (handled by Docusaurus frontmatter)
- Fix spelling: queing→queuing, ocurring→occurring, reliablity→reliability,
  retriving→retrieving, worklfows→workflows, IDResuePolicy→IDReusePolicy
- Fix grammar: it's state→its state, make make→make, relay on→rely on
- Fix punctuation and formatting consistency
- Update cadence-web URL from uber/cadence-web to cadence-workflow/cadence-web
- Remove internal Uber link from workflow-queries-formatted-data.md
- Fix frontmatter formatting in mutual-tls.md

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs: proofread docs/04-java-client/ folder

- Remove H1 headers (handled by Docusaurus frontmatter)
- Fix spelling: ExperiationInterval to ExpirationInterval, utilises to utilizes,
  initialised to initialized, sate to state
- Fix grammar: recommend to use to recommend using, MUST NOT passing to MUST NOT pass,
  a incompatible to an incompatible, written since to written as if
- Fix article usage: an com.uber to a com.uber
- Fix incomplete sentence in queries.md

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs: proofread docs/05-go-client/ folder

- Remove H1 headers (handled by Docusaurus frontmatter)
- Fix spelling: utilising to utilizing, programing to programming, erorrs to errors
- Fix grammar: There two parts to There are two parts, functions needs to functions need
- Fix capitalization: build-in to built-in, golang to Go
- Fix typos: ExecuteChildworkflow to ExecuteChildWorkflow, the the to the
- Fix verb agreement: heartbeat its to heartbeats its, method is to method are
- Fix tense: send to sent in testing signals section
- Fix code comments: # to // for Go syntax

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* docs: proofread remaining docs folders (codelabs, cli, operation-guide, workflow-troubleshooting, releases, about)

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

* blog: proofread all blog posts (fix typos, grammar, broken links)

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

---------

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>

Author: Bueller87

README.md

@@ -6,7 +6,7 @@
 
 [Cadence docs](https://cadenceworkflow.io) is built using [Docusaurus](https://docusaurus.io/).
 
-> 📚 **New to contributing to Cadence?** Check out our [Contributing Guide](https://cadenceworkflow.io/community/how-to-contribute/getting-started) for an overview of the contribution process across all Cadence repositories. This document contains cadence backend specific setup and development instructions.
+> 📚 **New to contributing to Cadence?** Check out our [Contributing Guide](https://cadenceworkflow.io/community/how-to-contribute/getting-started) for an overview of the contribution process across all Cadence repositories. This document contains Cadence backend specific setup and development instructions.
 
 ### Installation
 
@@ -35,19 +35,19 @@ This command generates static content into the `build` directory and can be serv
 In order to deploy to multiple environments, some configuration options in `docusaurus.config.ts` are made available for override through environment variables.
 
 ```bash
-# Can be replaced by your GH pages url, ie. https://<userId>.github.io/
+# Can be replaced by your GH pages URL, i.e., https://<userId>.github.io/
 CADENCE_DOCS_URL=https://cadenceworkflow.io
 
 # For GitHub pages deployment, it is often /<projectName>/ defaults to `/`
 BASE_URL=/cadence-docs/
 
-# For Github pages only, this is your Github org/user name.
+# For GitHub pages only, this is your GitHub org/user name.
 ORGANIZATION_NAME=cadence-workflow
 ```
 
 #### CNAME
 
-A file `static/CNAME` should be present in order to deploy to a [github pages site that uses a custom domain](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site). I.E. cadenceworkflow.io
+A file `static/CNAME` should be present in order to deploy to a [GitHub pages site that uses a custom domain](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site), i.e., cadenceworkflow.io.
 This file is created by the deploy action, but if deploying from a local environment, care should be taken to ensure the file exists.
 
 ### Deployment
@@ -69,10 +69,10 @@ If you are using GitHub pages for hosting, this command is a convenient way to b
 
 ### Updating Release Data
 
-The release pages rely on data from GitHub that is persisted as json files under `static/data/releases/`.
+The release pages rely on data from GitHub that is persisted as JSON files under `static/data/releases/`.
 In order to update the release information for display, this can be done manually or be set up as part of the CI/CD process by running the `scripts/fetch-releases.sh` script. Script uses the [GitHub CLI](https://cli.github.com/) to fetch the release data.
 
-Automatic updates to release data are performed by a github action `fetch-release-data`. Which will check if new data is available, and if so update the release data with the latest information and open a branch named `fetch-release-data` and open a PR if one is not open already.
+Automatic updates to release data are performed by a GitHub Action `fetch-release-data`, which will check if new data is available, and if so, update the release data with the latest information and open a branch named `fetch-release-data` and open a PR if one is not open already.
 
 Manual approval is required before merging and continuing to deployment.
 

blog/2022-05-31-community-spotlight-update-may-2022.md

@@ -29,7 +29,7 @@ We are always looking for ways to encourage project participation.  It doesn't m
 
 ## Share Your News!
 
-Our #support [Slack](http://t.uber.com/cadence-slack) channel is always full of questions and activity so we know that there are are lot of people out there exploring, trying out and setting up Cadence. We are always interested in hearing about what the community are doing so if you have something to you want to share as a blog post or part of this montly update then please contact us in the #community [Slack](http://t.uber.com/cadence-slack) channel.
+Our #support [Slack](http://t.uber.com/cadence-slack) channel is always full of questions and activity so we know that there are are lot of people out there exploring, trying out and setting up Cadence. We are always interested in hearing about what the community are doing so if you have something you want to share as a blog post or part of this monthly update then please contact us in the #community [Slack](http://t.uber.com/cadence-slack) channel.
 
 ## Next Cadence Technical Office Hours: 3rd and  27th June 2022
 

blog/2022-06-30-community-spotlight-update-june-2022.md

@@ -27,7 +27,7 @@ If you have any ideas or comments about how we can improve our community office
 
 ## Cadence Stability Improvements
 
-Is Cadence getting better? Yes it is! Many of you may have noticed that Cadence is improving.That is because of the amount of work being done behind the scenes. The Cadence core team has been doing a lot of work to stabilise Cadence functionality. Keep watching out for even more improvements!
+Is Cadence getting better? Yes it is! Many of you may have noticed that Cadence is improving. That is because of the amount of work being done behind the scenes. The Cadence core team has been doing a lot of work to stabilise Cadence functionality. Keep watching out for even more improvements!
 
 ## Sprechen Sie Deutsch?
 

blog/2022-08-31-community-spotlight-august-2022.md

@@ -44,7 +44,7 @@ If you are interested in speaking at our next meetup then please contact [Ender
 
 ## Looking for a Cadence Role?
 
-The Cadence teeam at Uber are recruiting for a Fullstack Engineer. If you are interested then please contact [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) for more details.
+The Cadence team at Uber is recruiting for a Fullstack Engineer. If you are interested then please contact [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) for more details.
 
 ## Cadence in the News!
 

blog/2022-09-30-community-spotlight-september-2022.md

@@ -15,7 +15,7 @@ Please see below for a roundup of the highlights:
 
 A Cadence talk by [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) and [Ben Slater](https://www.linkedin.com/in/ben-slater-2720562/) has been accepted for [Developer Week Enterprise](https://www.developerweek.com/global/conference/enterprise/).
 
-The talk is scheduled to for 16th November so please make a note in your calendars.
+The talk is scheduled for 16th November so please make a note in your calendars.
 
 # Sharing Knowledge
 

blog/2022-10-31-community-spotlight-october-2022.md

@@ -15,19 +15,19 @@ Please see below for a roundup of the highlights:
 
 It's always great to get the community together and we had planned to run another Cadence Meetup in early November. Unfortunately we didn't have enough time to get things organised so we've decided to postpone it. So please watch out for an announcement for the new Cadence meetup date.
 
-## Doordash Technnical Showcase Featuring Cadence
+## DoorDash Technical Showcase Featuring Cadence
 
 We have had some great feedback from people who attended Technical Showcase that was run this month by Doordash. It featured their financial products but also highlighted some of the key technologies they use...and guess what Cadence is one of them!
 
-If you missed the session then you will be happy to know that it was recorded and we've inlcuded a link to the [the recording on Youtube](https://www.youtube.com/watch?v=uNwbdQyLpns).
+If you missed the session then you will be happy to know that it was recorded and we've included a link to [the recording on YouTube](https://www.youtube.com/watch?v=uNwbdQyLpns).
 
 Thanks to the Doordash team for running the session and helping support Cadence by sharing their knowledge.
 
 <!-- truncate -->
 
 ## iWF Support for Cadence ##
 
-Community member [Quanzheng Long](https://www.linkedin.com/in/prclqz/) has been busy working on a new project that has been built on top of Cadence. The project is called [iWF - Interpreter for Workflow](https://github.com/indeedeng/iwf). It's great to see that Cadence is now growing it's own ecosystem!
+Community member [Quanzheng Long](https://www.linkedin.com/in/prclqz/) has been busy working on a new project that has been built on top of Cadence. The project is called [iWF - Interpreter for Workflow](https://github.com/indeedeng/iwf). It's great to see that Cadence is now growing its own ecosystem!
 
 Please feel free to take a look and let Long know what you think!
 

blog/2022-11-30-community-spotlight-november-2022.md

@@ -15,13 +15,13 @@ Please see below for a roundup of the highlights:
 
 This month Uber Engineering published a really nice article on one of the ways they are using Cadence. The article is called [How Uber Optimizes the Timing of Push Notifications using ML and Linear Programming](https://www.uber.com/en-US/blog/how-uber-optimizes-push-notifications-using-ml/).
 
-The Uber team take you through the details of the problem that they are looking to solve, so you can understand the scope limitations and depedencies - so please take a look.
+The Uber team take you through the details of the problem that they are looking to solve, so you can understand the scope, limitations, and dependencies - so please take a look.
 
 ## Cadence @ DeveloperWeek Enterprise ##
 
-DevNetwork run a series of conferences and during November Cadence was featured in at [DeveloperWeek Enterprise](https://www.developerweek.com/global/conference/enterprise/). [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) and [Ben Slater](https://www.linkedin.com/in/ben-slater-2720562/) presented a talk called [Espress Complex Business Logic as Code with Open Source Cadence!](https://embed.emamo.com/event/developerweek-enterprise-2022/s/express-complex-business-logic-as-code-with-open-source-cadence-WKLMvo).
+DevNetwork run a series of conferences and during November Cadence was featured in at [DeveloperWeek Enterprise](https://www.developerweek.com/global/conference/enterprise/). [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) and [Ben Slater](https://www.linkedin.com/in/ben-slater-2720562/) presented a talk called [Express Complex Business Logic as Code with Open Source Cadence!](https://embed.emamo.com/event/developerweek-enterprise-2022/s/express-complex-business-logic-as-code-with-open-source-cadence-WKLMvo).
 
-It is good to see that we are finding new channels for us to present the benefits of using Cadence. Huge hanks to Ben and Ender for the presentation and to everyone that attended.
+It is good to see that we are finding new channels for us to present the benefits of using Cadence. Huge thanks to Ben and Ender for the presentation and to everyone that attended.
 
 <!-- truncate -->
 

blog/2023-01-31-community-spotlight-january-2023.md

@@ -22,7 +22,7 @@ Please remember that if you have question about Cadence or are facing a specific
 ## Update on iWF Support for Cadence ##
 Last October we featured an update in our monthly blog about [iWF - Interpreter for Workflow](https://github.com/indeedeng/iwf), a project built on top of Cadence by community member [Quanzheng Long](https://www.linkedin.com/in/prclqz/). It was announced recently that iWF has released a [Golang SDK](https://github.com/iworkflowio/iwf-golang-sdk) and updated  versions of the [Java SDK and server](https://github.com/indeedeng/iwf).
 
-Long is really keen to get feedback so please take a look at iWF, try them out and presented him any feedback.
+Long is really keen to get feedback so please take a look at iWF, try it out and present him with any feedback.
 Long has also created a couple of blog posts about iWF that we have featured in the Cadence in the News section below so please take a look.
 
 ## Cadence in the News!

blog/2023-03-31-community-spotlight-march-2023.md

@@ -16,7 +16,7 @@ We are very pleased to let you know that a talk on Cadence has been accepted for
 The talk called [Cadence: The New Open Source Project for Building Complex Distributed Applications](https://ossna2023.sched.com/event/1K5B1) will be given by [Ender Demirkaya](https://www.linkedin.com/in/enderdemirkaya/) and [Emrah Seker](https://www.linkedin.com/in/emrahseker/) If you are planning to attend the Open Source Summit then please don't forget to attend the talk and take time catch up with Ender and Emrah!
 
 ## Community Activity ##
-Our Slack #support channel has been very active over the last few months as we continue to get an continual stream of questions. Here are the stats:
+Our Slack #support channel has been very active over the last few months as we continue to get a continual stream of questions. Here are the stats:
 
 - February 2023 : 16 questions asked
 - March 2023 : 12 questions asked

blog/2023-07-16-write-your-first-workflow-with-cadence/2023-07-16-write-your-first-workflow-with-cadence.md

@@ -8,7 +8,7 @@ tags:
   - introduction-to-cadence
 ---
 
-We have covered [basic components of Cadence](/blog/2023-06-28-components-of-cadence-application-setup.md) and [how to implement a Cadence worker on local environment](/blog/2023-07-05-implement-cadence-worker-from-scratch.md) in previous blogs. In this blog, let's write your very first HelloWorld workflow with Cadence. I've started the Cadence backend server in background and registered a domain named `test-domain`. You may use the code snippet for the worker service in [this blog](/blog/2023-07-05-implement-cadence-worker-from-scratch.md)  Let's first write a activity, which takes a single string argument and print a log in the console.
+We have covered [basic components of Cadence](/blog/2023-06-28-components-of-cadence-application-setup.md) and [how to implement a Cadence worker on local environment](/blog/2023-07-05-implement-cadence-worker-from-scratch.md) in previous blogs. In this blog, let's write your very first HelloWorld workflow with Cadence. I've started the Cadence backend server in background and registered a domain named `test-domain`. You may use the code snippet for the worker service in [this blog](/blog/2023-07-05-implement-cadence-worker-from-scratch.md). Let's first write an activity, which takes a single string argument and prints a log in the console.
 
 ```go
 func helloWorldActivity(ctx context.Context, name string) (string, error) {