docs: capitalize hasura features

## Description

[Jira ticket](https://hasurahq.atlassian.net/jira/software/projects/DOCS/boards/19?selectedIssue=DOCS-102).

This PR capitalizes Hasura features based on our [feature capitalization guide on the docs wiki](https://hasura.io/docs/wiki/style/hasura-features/).

It also introduces some linting by prettier.

PR-URL: hasura/graphql-engine-mono#7260
Co-authored-by: Samir Talwar <[email protected]>
Co-authored-by: Luca Restagno <[email protected]>
Co-authored-by: hasura-bot <[email protected]>
Co-authored-by: Gil Mizrahi <[email protected]>
Co-authored-by: Stefano Magni <[email protected]>
Co-authored-by: Daniel Harvey <[email protected]>
Co-authored-by: Abby Sassel <[email protected]>
Co-authored-by: Daniele Cammareri <[email protected]>
Co-authored-by: Brandon Martin <[email protected]>
GitOrigin-RevId: 5946f313cb44c639fac61e6c7fb44f704ee2a709

Author: 10 people

docs/.gitignore

@@ -25,4 +25,6 @@ yarn-error.log*
 !.yarn/plugins
 !.yarn/releases
 !.yarn/sdks
-!.yarn/versions
+!.yarn/versions
+
+.tool-versions

docs/CONTRIBUTING.md

@@ -15,11 +15,11 @@ Issues also marked as `help wanted` (see
 are those that require community contributions.
 
 Please note that some of these issues, labelled with both `c/docs` and `c/console`/`c/server`, are part of a change/task
-that requires modifications in some component of GraphQL engine and the docs.
+that requires modifications in some component of GraphQL Engine and the docs.
 
 Feel free to open pull requests to address these issues or to add/fix docs features/content, even if a corresponding
 issue doesn't exist. If you are unsure about whether to go ahead and work on something like the latter, please get in
-touch with the maintainers in the `GraphQL engine`->`contrib` channel in the community
+touch with the maintainers in the `GraphQL Engine`->`contrib` channel in the community
 [Discord](https://discord.gg/vBPpJkS).
 
 ## Notes

docs/docs/account-management/billing/billing-data-calculation.mdx

@@ -26,7 +26,7 @@ the operations that are performed by you, your apps, or your clients.
 
 The data pass-through is calculated by analyzing the logs that are sent from your project. All data transfer from Hasura
 Cloud to external networks - such as your database server, external webhooks for [Actions](/actions/index.mdx),
-[event triggers](/event-triggers/index.mdx), [scheduled triggers](/scheduled-triggers/index.mdx) or your
+[Event Triggers](/event-triggers/index.mdx), [Scheduled Triggers](/scheduled-triggers/index.mdx) or your
 [Remote Schema](/remote-schemas/index.mdx) - is accounted for in Hasura Cloud billing.
 
 We account for the following types of logs in Hasura Cloud data pass-through:
@@ -47,7 +47,7 @@ We account for the following types of logs in Hasura Cloud data pass-through:
   calculating your data usage. This log is generated when Hasura triggers an external webhook.
 
 - `scheduled-trigger-log`: The sizes of the request and response of the `scheduled-trigger-log` are taken into account
-  for calculating your data usage. The cost incurred by this depends on the frequency of scheduled triggers.
+  for calculating your data usage. The cost incurred by this depends on the frequency of Scheduled Triggers.
 
 These logs are used to calculate your data usage in Hasura Cloud, which is then used for generating monthly invoices.
 You can find more information about the pricing for data pass-through [on our pricing page](https://hasura.io/pricing/).

docs/docs/actions/action-handlers.mdx

@@ -180,17 +180,17 @@ For your action, add a header that will act as an action secret.
 <Tabs groupId="user-preference" className="api-tabs">
 <TabItem value="console" label="Console">
 
-Head to the `Actions -> [action-name]` tab in the console and scroll down to `Headers`. You can now configure an action
+Head to the `Actions -> [action-name]` tab in the Console and scroll down to `Headers`. You can now configure an action
 secret by adding a header:
 
-<Thumbnail src='/img/actions/action-secret-header.png' alt='Console action secret' width='700px' />
+<Thumbnail src="/img/actions/action-secret-header.png" alt="Console action secret" width="700px" />
 
 Then hit `Save`.
 
 </TabItem>
 <TabItem value="cli" label="CLI">
 
-Go to `metadata/actions.yaml` in the Hasura project directory.
+Go to `metadata/actions.yaml` in the Hasura Project directory.
 
 Update the definition of your action by adding the action secret as a header:
 
@@ -212,7 +212,7 @@ Save the changes and run `hasura metadata apply` to set the headers.
 <TabItem value="api" label="API">
 
 Headers can be set when [creating](/api-reference/metadata-api/actions.mdx#metadata-create-action) or
-[updating](/api-reference/metadata-api/actions.mdx#metadata-update-action) an action via the metadata API.
+[updating](/api-reference/metadata-api/actions.mdx#metadata-update-action) an action via the Metadata API.
 
 ```http {12-17}
 POST /v1/metadata HTTP/1.1
@@ -251,8 +251,8 @@ X-Hasura-Role: admin
 :::info Note
 
 Before creating an action via the
-[create_action metadata API](/api-reference/metadata-api/actions.mdx#metadata-create-action), all custom types need to
-be defined via the [set_custom_types](/api-reference/metadata-api/custom-types.mdx#metadata-set-custom-types) metadata
+[create_action Metadata API](/api-reference/metadata-api/actions.mdx#metadata-create-action), all custom types need to
+be defined via the [set_custom_types](/api-reference/metadata-api/custom-types.mdx#metadata-set-custom-types) Metadata
 API.
 
 :::

docs/docs/actions/action-permissions.mdx

@@ -1,7 +1,7 @@
 ---
 sidebar_label: Actions permissions
 sidebar_position: 7
-description: Permissions for Hasura actions
+description: Permissions for Hasura Actions
 keywords:
   - hasura
   - docs
@@ -24,16 +24,16 @@ As with the other fields in the GraphQL schema, users need to be given access to
 <Tabs groupId="user-preference" className="api-tabs">
 <TabItem value="console" label="Console">
 
-Head to the `Actions -> [action-name] -> Permissions` tab in the console.
+Head to the `Actions -> [action-name] -> Permissions` tab in the Console.
 
-<Thumbnail src='/img/actions/actions-permissions.png' alt='Console action permission' />
+<Thumbnail src="/img/actions/actions-permissions.png" alt="Console action permission" />
 
 Hit `Save` to give the role permission to access the action.
 
 </TabItem>
 <TabItem value="cli" label="CLI">
 
-Go to `metadata/actions.yaml` in the Hasura project directory.
+Go to `metadata/actions.yaml` in the Hasura Project directory.
 
 Update the definition of the `insertAuthor` action as:
 
@@ -54,7 +54,7 @@ Save the changes and run `hasura metadata apply` to set the permissions.
 <TabItem value="api" label="API">
 
 Action permissions can be set by using the
-[create_action_permission](/api-reference/metadata-api/actions.mdx#metadata-create-action-permission) metadata API:
+[create_action_permission](/api-reference/metadata-api/actions.mdx#metadata-create-action-permission) Metadata API:
 
 ```http
 POST /v1/metadata HTTP/1.1

docs/docs/actions/action-relationships.mdx

@@ -1,7 +1,7 @@
 ---
 sidebar_label: Actions relationships
 sidebar_position: 8
-description: Manage Hasura actions relationships
+description: Manage Hasura Actions relationships
 keywords:
   - hasura
   - docs
@@ -82,18 +82,18 @@ You can create relationships for custom output types by:
 <Tabs groupId="user-preference" className="api-tabs">
 <TabItem value="console" label="Console">
 
-Head to the `Actions -> [action-name] -> Relationships` tab in the console for the action returning the output type.
+Head to the `Actions -> [action-name] -> Relationships` tab in the Console for the Action returning the output type.
 
 Set the output type relationship as shown below:
 
-<Thumbnail src='/img/actions/actions-relationship.png' alt='Console action relationship' />
+<Thumbnail src="/img/actions/actions-relationship.png" alt="Console action relationship" />
 
 Hit `Save` to create the relationship.
 
 </TabItem>
 <TabItem value="cli" label="CLI">
 
-Go to `metadata/actions.yaml` in the Hasura project directory.
+Go to `metadata/actions.yaml` in the Hasura Project directory.
 
 Update the definition of the `UpdateAuthorOutput` object type as:
 
@@ -117,7 +117,7 @@ Save the changes and run `hasura metadata apply` to create the relationship.
 <TabItem value="api" label="API">
 
 Action relationships can be added while defining custom types via the
-[set_custom_types](/api-reference/metadata-api/custom-types.mdx#metadata-set-custom-types) metadata API:
+[set_custom_types](/api-reference/metadata-api/custom-types.mdx#metadata-set-custom-types) Metadata API:
 
 ```http {20-29}
 POST /v1/metadata HTTP/1.1

docs/docs/actions/async-actions.mdx

@@ -23,7 +23,7 @@ query/subscribe to its status.
 
 :::info Note
 
-Only actions of type `mutation` can be async. Actions of type query are
+Only Actions of type `mutation` can be async. Actions of type query are
 always executed synchronously.
 
 :::
@@ -52,7 +52,7 @@ action using this `action id`.
 
 ```graphql
 subscription getPlaceOrderResponse {
-  place_order (id: "23b1c256-7aff-4b95-95bd-68220d9f93f2") {
+  place_order(id: "23b1c256-7aff-4b95-95bd-68220d9f93f2") {
     output
     errors
   }

docs/docs/actions/codegen/index.mdx

@@ -1,5 +1,5 @@
 ---
-description: Codegen for Hasura actions
+description: Codegen for Hasura Actions
 keywords:
   - hasura
   - docs
@@ -31,11 +31,11 @@ contributions from the community.
 <Tabs groupId="user-preference" className="api-tabs">
 <TabItem value="console" label="Console">
 
-Head to the `Actions -> [action-name] -> Codegen` tab in the console
+Head to the `Actions -> [action-name] -> Codegen` tab in the Console
 
 You can select the framework of your choice to get the corresponding handler boilerplate code.
 
-<Thumbnail src='/img/actions/console-codegen-tab.png' alt='Console codegen tab' />
+<Thumbnail src="/img/actions/console-codegen-tab.png" alt="Console codegen tab" />
 
 </TabItem>
 <TabItem value="cli" label="CLI">
@@ -52,14 +52,14 @@ hasura actions use-codegen
 
 1.  Choose which framework you want to codegen for:
 
-    <Thumbnail src='/img/actions/cli-framework-prompt.png' alt='CLI Framework Prompt' />
+    <Thumbnail src="/img/actions/cli-framework-prompt.png" alt="CLI Framework Prompt" />
 
 2.  Choose if you also wish to clone a starter kit for the chosen framework:
 
-    <Thumbnail src='/img/actions/cli-starter-kit-prompt.png' alt='CLI Starter Kit Prompt' />
+    <Thumbnail src="/img/actions/cli-starter-kit-prompt.png" alt="CLI Starter Kit Prompt" />
 
 3.  Choose a path where you want to output the auto-generated code files
-    <Thumbnail src='/img/actions/cli-output-dir-prompt.png' alt='CLI Starter Kit Prompt' />
+    <Thumbnail src="/img/actions/cli-output-dir-prompt.png" alt="CLI Starter Kit Prompt" />
 
 This command will update your `config.yaml` with the codegen config as per your preferences. You can also set these
 values manually in `config.yaml`.
@@ -95,7 +95,7 @@ The codegen files will be generated at the `output_dir` path from `config.yaml`.
 ## Codegen for your framework
 
 As of now, Hasura provides codegen for a few frameworks (`nodejs-express`, `typescript-zeit`, `python-flask` and many
-more). You can see the full list in the `Codegen` tab on the console after you've
+more). You can see the full list in the `Codegen` tab on the Console after you've
 [created an action](/actions/create.mdx).
 
 We will continue adding more examples to the documentation.

docs/docs/actions/codegen/python-flask.mdx

@@ -1,7 +1,7 @@
 ---
 sidebar_label: Python & Flask
 sidebar_position: 1
-description: Codegen for Hasura actions in Python & Flask
+description: Codegen for Hasura Actions in Python & Flask
 keywords:
   - hasura
   - docs
@@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
 
 ## Introduction
 
-This page describes how to use Hasura actions and codegen to build a Python & Flask API for JWT authentication.
+This page describes how to use Hasura Actions and codegen to build a Python & Flask API for JWT authentication.
 
 ## Step 1: Create action definition & custom types
 
@@ -56,10 +56,10 @@ type JsonWebToken {
 Example: creating the `Signup` action
 
 <Thumbnail
-  src='/img/actions/python-flask-signup-types.png'
-  alt='Python Flask signup types'
-  width='1000px'
-  className='no-shadow'
+  src="/img/actions/python-flask-signup-types.png"
+  alt="Python Flask signup types"
+  width="1000px"
+  className="no-shadow"
 />
 
 ## Step 2: Action handler implementation for signup
@@ -347,7 +347,7 @@ $ decode_jwt 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwib
 
 ## Step 5: Calling the finished actions
 
-Try out your defined actions from the GraphQL API.
+Try out your defined Actions from the GraphQL API.
 
 Call the `Signup` action: