Merge pull request #2752 from port-labs/PORT-9667-docs-blueprint-structure-table-some-notes-are-actually-descriptions

hadar-co · web-flow · commit 618330098ad8 · 2025-09-01T11:33:40.000+03:00
Added the suggested changes to the sctructure table.
diff --git a/archive/complete-use-cases/_iac-templates.md b/archive/complete-use-cases/_iac-templates.md
@@ -71,7 +71,7 @@ Forwarding                    https://1234-5678-9101-112-1314-1516-abcd-efgh-ijk
 
 Keep the `Forwarding URL` for later use.
 
-### Setup Port resources
+### Set up Port resources
 
 First, set up a Blueprint for an S3 bucket in Port.
 
diff --git a/docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/setup-ui-for-action.md b/docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/setup-ui-for-action.md
@@ -1,5 +1,5 @@
 ---
-title: Setup Actions
+title: Set up Actions
 ---
 
 import ApiRef from "/docs/api-reference/\_learn_more_reference.mdx";
@@ -8,7 +8,7 @@ import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
 import PortTooltip from "/src/components/tooltip/tooltip.jsx"
 
-# Setup frontend
+# Set up frontend
 
 <center>
 
diff --git a/docs/actions-and-automations/setup-backend/webhook/examples/terraform-no-code-resource-provisioning.md b/docs/actions-and-automations/setup-backend/webhook/examples/terraform-no-code-resource-provisioning.md
@@ -71,7 +71,7 @@ Forwarding                    https://1234-5678-9101-112-1314-1516-abcd-efgh-ijk
 
 Keep the `Forwarding URL` for later use.
 
-### Setup Port resources
+### Set up Port resources
 
 First, set up a [blueprint](/build-your-software-catalog/customize-integrations/configure-data-model/setup-blueprint/setup-blueprint.md) for an S3 bucket in Port.
 
diff --git a/docs/build-your-software-catalog/customize-integrations/configure-data-model/setup-blueprint/setup-blueprint.md b/docs/build-your-software-catalog/customize-integrations/configure-data-model/setup-blueprint/setup-blueprint.md
@@ -1,15 +1,15 @@
 ---
 sidebar_position: 1
-title: Setup Blueprints
-sidebar_label: Setup Blueprints
+title: Set up Blueprints
+sidebar_label: Set up Blueprints
 ---
 
 import ApiRef from "/docs/api-reference/\_learn_more_reference.mdx";
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
 
-# Setup Blueprints
+# Set up blueprints
 
 <center>
 
@@ -313,13 +313,13 @@ Each blueprint is represented by a [Json schema](https://json-schema.org/), as s
 
 | Field                   | Description                                                                                                               | Notes                                                                                                                   |
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
-| `identifier`            | Unique identifier                                                                                                         | **Required**. The identifier is used for API calls, programmatic access and distinguishing between different blueprints |
-| `title`                 | Name                                                                                                                      | **Required**. Human-readable name for the blueprint                                                                     |
-| `description`           | Description                                                                                                               | The value is visible as a tooltip to users when hovering over the info icon in the UI                                   |
-| `icon`                  | Icon for the blueprint and entities of the blueprint.                                                                     | See the full icon list [below](#full-icon-list)                                                                         |
-| `calculationProperties` | Contains the properties defined using [calculation properties](./properties/calculation-property/calculation-property.md) | **Required**                                                                                                            |
-| `mirrorProperties`      | Contains the properties defined using [mirror properties](./properties/mirror-property)                |                                                                                                                         |
-| `schema`                | An object containing two nested fields: `properties` and `required`.                                                      | **Required**. See the schema structure [here](#schema-object)                                                           |
+| `identifier`            | The identifier is used for API calls, programmatic access and distinguishing between different blueprints.                | **Required**  |
+| `title`                 | Human-readable name for the blueprint.                                                                                    |**Required**                                                                     |
+| `description`           | The value is visible as a tooltip to users when hovering over the info icon in the UI.   |                                    |
+| `icon`                  | Icon for the blueprint and entities of the blueprint.                                                                     | See the full icon list [below](#full-icon-list).                                                                        |
+| `calculationProperties` | Contains the properties defined using [calculation properties](./properties/calculation-property/calculation-property.md). | **Required**                                                                                                            |
+| `mirrorProperties`      | Contains the properties defined using [mirror properties](./properties/mirror-property).                |                                                                                                                         |
+| `schema`                | An object containing two nested fields: `properties` and `required`.                                                      | **Required**. See the schema structure [here](#schema-object).                                                           |
 
 :::tip Available properties
 All available properties are listed in the [properties](./properties/properties.md) page
diff --git a/docs/guides/all/create-cloud-resource-using-iac.md b/docs/guides/all/create-cloud-resource-using-iac.md
@@ -45,7 +45,7 @@ In this guide we will add a new property to our `Repository` <PortTooltip id="bl
 
 This property is empty for now in all repositories, we will fill it as part of the action we're about to create 😎
 
-## Setup the action's frontend
+## Set up the action's frontend
 
 1. Head to the [Self-service page](https://app.getport.io/self-serve) of your portal.
 2. Click on the `+ Action` button in the top-right corner :
@@ -222,7 +222,7 @@ The last step is customizing the action's permissions. For simplicity's sake, we
 
 The action's frontend is now ready 🥳
 
-## Setup the action's backend
+## Set up the action's backend
 
 Now we want to write the logic that our action will trigger.
 
diff --git a/docs/guides/all/let-developers-enrich-services-using-gitops.md b/docs/guides/all/let-developers-enrich-services-using-gitops.md
@@ -342,7 +342,7 @@ Then, fill out your workflow details:
 
 The last step is customizing the action's permissions. For simplicity's sake, we will use the default settings. For more information, see the [permissions](/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac/) page. Click `Create`.
 
-### Setup the action's backend
+### Set up the action's backend
 
 Our action will create a pull-request in the  repository, containing a `port.yml` file that will add data to the repository in Port. Choose a backend type below to setup the workflow:
 
diff --git a/docs/guides/all/scaffold-a-new-service.md b/docs/guides/all/scaffold-a-new-service.md
@@ -33,7 +33,7 @@ The action we will create in this guide will:
 
 ## Implementation
 
-###  Setup the action's frontend
+###  Set up the action's frontend
 
 1. Head to the [Self-service page](https://app.getport.io/self-serve) of your portal.
 2. Click on the `+ Action` button in the top-right corner (or in the middle if there are no actions yet):
@@ -253,7 +253,7 @@ The action's frontend is now ready 🥳
 
 <br/>
 
-### Setup the action's backend
+### Set up the action's backend
 
 Now we want to write the logic that our action will trigger.
 
diff --git a/docs/guides/all/setup-slack-reminders.md b/docs/guides/all/setup-slack-reminders.md
@@ -31,7 +31,7 @@ Once implemented:
 
 ## Implementation
 
-### Setup the action's frontend
+### Set up the action's frontend
 
 1. Head to the [Self-service page](https://app.getport.io/self-serve) of your portal.
 2. Click on the `+ Action` button on the top left corner :
@@ -120,7 +120,7 @@ The action's frontend is now ready 🥳
 
 <br/>
 
-### Setup the action's backend
+### Set up the action's backend
 
 Now we want to write the logic that our action will trigger:
 
diff --git a/docs/scorecards/overview.md b/docs/scorecards/overview.md
@@ -4,7 +4,7 @@ title: Overview
 sidebar_label: Overview
 ---
 
-# Promote scorecards
+# Scorecards
 
 ## What is a Scorecard?
 
diff --git a/docs/solutions/resource-self-service/setup-approval-workflows.md b/docs/solutions/resource-self-service/setup-approval-workflows.md
@@ -3,7 +3,7 @@ title: "Setup approval workflows"
 sidebar_position: 4
 ---
 
-# Setup approval workflows
+# Set up approval workflows
 
 Effective platform engineering requires oversight at every level—whether it's a human developer requesting a production database or an AI agent automatically scaling infrastructure. Without proper controls, self-service can quickly become a security and compliance nightmare. Port provides three complementary layers of governance: Role-Based Access Control (RBAC) for user permissions, approval workflows for human oversight, and dynamic permissions for context-aware access control.
 
