diff --git a/content/en/docs/dependencies/_index.md b/content/en/docs/dependencies/_index.md
index 61a7e060..b06f5d66 100644
--- a/content/en/docs/dependencies/_index.md
+++ b/content/en/docs/dependencies/_index.md
@@ -30,23 +30,8 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
   db:
     type: postgres
-    properties:
-      host:
-        default: localhost
-      port:
-        default: 5432
-      name:
-        default: postgres
-      user:
-        secret: true
-      password:
-        secret: true
   service-b:
     type: workload
 ```
@@ -70,10 +55,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 To prepare the Docker Compose configuration files, convert both Score files with `score-compose`.
diff --git a/content/en/docs/dependencies/dependencies-humanitec.md b/content/en/docs/dependencies/dependencies-humanitec.md
index 2827e439..1ace96eb 100644
--- a/content/en/docs/dependencies/dependencies-humanitec.md
+++ b/content/en/docs/dependencies/dependencies-humanitec.md
@@ -43,25 +43,10 @@ containers:
 resources:
   db:
     type: postgres
-    properties:
-      host:
-        default: localhost
-      port:
-        default: 5432
-      name:
-        default: postgres
-      user:
-        secret: true
-      password:
-        secret: true
   dns:
     type: dns
-    properties:
-      domain:
   backend:
     type: workload
-    properties:
-      name:
 ```
 
 This example also uses an extensions file, called `humanitec.yaml`, that contains additional hints for `score-humanitec` CLI tool. This information would help the CLI tool to resolve the resources properly.
diff --git a/content/en/docs/environment variables/environment-variables-compose.md b/content/en/docs/environment variables/environment-variables-compose.md
index 3e3b2721..efa4a7fb 100644
--- a/content/en/docs/environment variables/environment-variables-compose.md	
+++ b/content/en/docs/environment variables/environment-variables-compose.md	
@@ -36,10 +36,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 Use the `run` command to generate a Docker Compose file from Score.
diff --git a/content/en/docs/environment variables/environment-variables-helm.md b/content/en/docs/environment variables/environment-variables-helm.md
index ba0f3b4b..20ab6b62 100644
--- a/content/en/docs/environment variables/environment-variables-helm.md	
+++ b/content/en/docs/environment variables/environment-variables-helm.md	
@@ -31,10 +31,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 {{% alert %}}
diff --git a/content/en/docs/environment variables/environment-variables-humanitec.md b/content/en/docs/environment variables/environment-variables-humanitec.md
index 7ae3c98e..ed21877d 100644
--- a/content/en/docs/environment variables/environment-variables-humanitec.md	
+++ b/content/en/docs/environment variables/environment-variables-humanitec.md	
@@ -29,10 +29,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 {{% alert %}}
diff --git a/content/en/docs/extensions/_index.md b/content/en/docs/extensions/_index.md
index 812d0172..cf0ff269 100644
--- a/content/en/docs/extensions/_index.md
+++ b/content/en/docs/extensions/_index.md
@@ -70,14 +70,8 @@ containers:
 resources:
   dns:
     type: dns
-    properties:
-      domain:
-      ...
   api-route:
     type: route
-    properties:
-      prefix:
-      ...
 ```
 
 ## Humanitec Workload implementation
diff --git a/content/en/docs/extensions/implement-ports-volumes.md b/content/en/docs/extensions/implement-ports-volumes.md
index f2ed5be8..03391687 100644
--- a/content/en/docs/extensions/implement-ports-volumes.md
+++ b/content/en/docs/extensions/implement-ports-volumes.md
@@ -31,11 +31,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      MESSAGE:
-        type: string
-      DATADOG_ENV:
-        type: string
   dns:
     type: dns
 ```
diff --git a/content/en/docs/get started/Transform/_index.md b/content/en/docs/get started/Transform/_index.md
deleted file mode 100644
index 915fe836..00000000
--- a/content/en/docs/get started/Transform/_index.md	
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: "Run your first transform"
-linkTitle: "Run your first transform"
-weight: 4
-draft: true
-description: >
-  This section contains pages that show how to apply a transformation on your Score Specification file.
----
-
-Throughout the following sections. You will learn how to run a transform in the following formats:
-
-<!--
-
-```yaml
-name: backend
-
-container:
-  image: registry.humanitec.io/humanitec-demo/paws-demo-backend
-  variables:
-    PORT: "8080"
-    DEBUG: "false"
-    CONNECTION_STRING: postgresql://${resources.database.username}:${resources.database.password}@${resources.database.host}:${resources.database.port}/${resources.database.name}
-
-resources:
-  database:
-    type: postgres
-    properties:
-      host:
-        required: true
-        default: localhost
-      port:
-        required: true
-        default: 5432
-      name:
-        required: true
-      username:
-        secret: true
-        required: false
-      password:
-        secret: true
-        required: false
-```
-
--->
diff --git a/content/en/docs/get started/Transform/docker.md b/content/en/docs/get started/Transform/docker.md
deleted file mode 100644
index 21b9bdcd..00000000
--- a/content/en/docs/get started/Transform/docker.md	
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: "Compose"
-linkTitle: "Compose"
-weight: 4
-description: >
-  Learn to translate a Score Specification file into a Docker Compose configuration with the target Score implementation tool.
----
-
-{{% alert %}}
-
-> If at any point you need help, `score-compose --help` from your terminal.
-> {{% /alert %}}
-
-In this walkthrough you will:
-
-- 1
-- 2
-- 3
-
-Getting started:
-Start files
-End files
-
-### Prerequisites: Set up
-
-1. Install the `score-compose` target Score implementation tool.
-
-## Step 1. Author your score file
-
-1. Declare your resources.
-   1. In this example, we will use a Postgres database.
-
-```yaml
-resources:
-db:
-  type: postgres
-```
-
-1. Add properties.
-
-```yaml
-properties:
-      host:
-        default: localhost
-      port:
-        default: 5432
-      name:
-      username:
-        secret: true
-      password:
-        secret: true
-```
-
-1. Declare your dependencies
-2. Add environment variables.
-
-## Step 2. Run the target Score implementation tool
-
-Choose from one of the following options:
-
-1. `score-compose`
-2. `score-helm`
-3. `score-humanitec`
-
-## Step 3. ?
-
-## Step 4. Push to CI
-
-By default, `--file` defaults to `./score.yaml` and `--output` defaults to `./compose.yaml`.
-
-The following is the expected output from the previous command.
-
-```bash
-Reading './score.yaml'...
-Parsing score spec...
-Building docker compose configuration...
-Creating './compose.yaml'...
-Writing docker compose configuration...
-```
-
-The following is the output of the run command.
-
-```yaml
-services:
-  hello-world: {}
-```
-
-**Results**: You've successfully transformed a Score Specification file into a Docker Compose configuration.
diff --git a/content/en/docs/get started/Transform/helm.md b/content/en/docs/get started/Transform/helm.md
deleted file mode 100644
index f8df3848..00000000
--- a/content/en/docs/get started/Transform/helm.md	
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Helm"
-linkTitle: "Helm"
-weight: 4
-description: >
-  Learn to translate a Score Specification file into a Helm configuration with the target Score implementation tool.
----
-
-{{% alert %}}
-
-> If at any point you need help, `score-helm --help` from your terminal.
-> {{% /alert %}}
-
-The Score Specification file configures into Helm values, including containers, dependencies, and other Helm specific values.
-
-These values are combined with a pre-built Helm directory that are shipped with the application by default.
-The `score-helm run` command produces a valid `values.yaml` file that can be distributed or deployed.
-
-<!-- Helm is a package manager for Kubernetes. >
diff --git a/content/en/docs/get started/Transform/humanitec.md b/content/en/docs/get started/Transform/humanitec.md
deleted file mode 100644
index 7dc408c0..00000000
--- a/content/en/docs/get started/Transform/humanitec.md	
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: "Humanitec"
-linkTitle: "Humanitec"
-weight: 4
-description: >
-  This page is an overview of Score for Humanitec.
----
-
-{{% alert %}}
-
-> If at any point you need help, `score-humanitec --help` from your terminal.
-
-{{% /alert %}}
-
-Use `score-humanitec` to run the target Score implementation tool and output the deployment delta details.
-
-To deploy an updated service to the remote environment with `score-humanitec` run the following command.
-
-```bash
-score-humanitec run \
-  -f ./backend/score.yaml \
-  --org humanitec-demo --app score-demo --env development --token $HT_TOKEN \
-  --image=registry.humanitec.io/humanitec-demo/score-demo-backend:0.3.0
-```
-
-The following is the output of the previous command.
-
-```json
-{
-  "id": "0025d1b6b90864ac3995998562e353290e458122",
-  "metadata": {
-    "env_id": "development",
-    "name": "PAWS-based deployment",
-    "created_by": "0110db28-90aa-4c42-bf52-9c49718da796",
-    "created_at": "2022-06-14T12:40:42.895793478Z",
-    "last_modified_at": "2022-06-14T12:40:42.895793478Z"
-  },
-  "modules": {
-    "add": {
-      "backend": {
-        "externals": {
-          "database": {
-            "type": "postgres"
-          }
-        },
-        "profile": "humanitec/default-module",
-        "spec": {
-          "containers": {
-            "backend": {
-              "id": "backend",
-              "image": "registry.humanitec.io/humanitec-demo/paws-demo-backend:0.3.0",
-              "variables": {
-                "CONNECTION_STRING": "postgresql://${externals.database.username}:${externals.database.password}@${externals.database.host}:${externals.database.port}/${externals.database.name}",
-                "DEBUG": "false",
-                "PORT": "8080"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-**Results**: you can now view and deploy this preview with the Humanitec Web UI or API.
-
-## Deploy with Humanitec Web UI
-
-The following steps will deploy the deployment delta to your Humanitec organization through the Web UI.
-
-## Deploy with Humanitec API
-
-The following steps will deploy the deployment delta to your Humanitec organization through the API.
diff --git a/content/en/docs/reference/score-cli/errors.md b/content/en/docs/reference/score-cli/errors.md
index ce6db609..2cf0cf29 100644
--- a/content/en/docs/reference/score-cli/errors.md
+++ b/content/en/docs/reference/score-cli/errors.md
@@ -88,10 +88,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 In the previous code snippet, the `variables` parameter is adjusted too far left. It should be aligned with the `image`, `command`, and `args` parameters.
@@ -113,10 +109,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 Alternatively, you could have the map of the variables set incorrectly.
@@ -140,10 +132,6 @@ containers:
 resources:
   env:
     type: environment
-    properties:
-      NAME:
-        type: string
-        default: World
 ```
 
 The `FRIEND` parameter is set to `resources.friend.NAME`, but that is not a valid path in the `resources` section.
diff --git a/content/en/docs/reference/score-spec-reference.md b/content/en/docs/reference/score-spec-reference.md
index dce83631..f0b4b3ce 100644
--- a/content/en/docs/reference/score-spec-reference.md
+++ b/content/en/docs/reference/score-spec-reference.md
@@ -66,7 +66,7 @@ Resources can be anything and Score doesn't differentiate resources by types. Th
 
 It is up to {{< glossary_tooltip text="Score implementation (CLI)" term_id="score" >}} to resolve the resource by name, type, or any other meta information available.
 
-### Resource properties
+### Resources
 
 ```yaml
 resources:
@@ -75,12 +75,6 @@ resources:
       annotations:                  # optional
         [annotation-name]: [value]
     type: [resource-type]
-    properties:                     # optional
-      [property-name]:
-        type: string                # optional
-        default: interface{}        # optional
-        required: [true | false]    # false by default
-        secret: [true | false]      # false by default
 ```
 
 **`resources`**: defines dependencies needed by the Workload.
@@ -102,18 +96,6 @@ resources:
 - **Type**: string.
 - **Constraints**: alphanumeric string.
 
-**`properties`**: specifies properties definition that are available to the resource. Set properties that can be referenced in other places in the Score Specification file. For more information, see [Referencing Resources](#referencing-resources).
-
-**`property-name`**: used to reference the resource property in other places in Score file.
-
-- **Type**: string.
-- **Constraints**: alphanumeric string.
-
-  - `default`: specifies a value that can be defined for the property.
-  - `type`: specifies a property type.
-  - `required`: specifies a property as required. If specified, but the value is missing or empty, the deployment will fail.
-  - `secret`: specifies a property value as a case-sensitive secret. Values can be sourced from Vaults.
-
 ### Reserved resource types
 
 In general, `resource-type` has no meaning for Score, but it can affect how the targeted Score implementation tool resolves the resource. The following conventions are _reserved_ resource types.
@@ -122,36 +104,19 @@ In general, `resource-type` has no meaning for Score, but it can affect how the
 | ------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `environment` | Translates to the environment variables references. For example: `${PROPERTY-NAME}`.                                            | Translates to the application values references. For example: `${values.property-name}`.                                                                     |
 | `volume`      | Translates into a reference to the external volume. This reference is usually used in a container’s volume mount specification. | Translates into a reference to the external volume. This reference is usually used in a container’s volume mount specification.                              |
-| `service`     | N/A                                                                                                                             | Translates to the module properties references. For example: `${modules.service-name.property-name}`.                                                        |
+| `service`     | N/A                                                                                                                             | Translates to the module properties references.                                                                                                              |
 | `workload`    | N/A                                                                                                                             | Reserved resource type. Its usage may lead to compatibility issues with future releases of [score-humanitec](https://github.com/score-spec/score-humanitec). |
 
 ### Referencing resources
 
-Resources are declared in the `containers` section of the Score file and must map to the YAML structure defined in the `resources` section to properly resolve.
-
-For example, the following resource would map to the structure of the resource section.
-
-```yaml
-${resources.resource-name.property-name}
-```
-
-```yml
-resources:
-  resource-name:
-    property-name: my-property-name
-```
-
-{{% alert %}}
-
-> If the referenced resource or its property has not been defined, the {{< glossary_tooltip text="Score implementation (CLI)" term_id="score" >}} should report a syntax error.
-
-{{% /alert %}}
+Resources declared in the resources section of a Score file can be used in substitution patterns in different places.
 
 ### Resource example
 
-It is up to the Score implementation (CLI) on how and when the resource reference is resolved, and when the referenced values' substitution occurs.
+The Score implementation (CLI) resolves resource references and performs value substitution in a specific manner.
 
-For example, `score-compose` would convert resource properties into environment variables references in a resulting `compose.yaml` configuration file, and produce a reference `.env` file that the user can then populate. For more information, see the [.env file](https://docs.docker.com/compose/environment-variables/#the-env-file).
+For example, when using the `score-compose` command, resource references within substitution patterns are replaced with corresponding environment variable references in the resulting `compose.yaml` configuration file. To gather all the required environment variables, you can utilize the `--env-file` command line parameter to generate a reference `.env` file. This file can be populated with the necessary values by the user.
+For more instructions, see to the [.env file documentation](https://docs.docker.com/compose/environment-variables/#the-env-file).
 
 The following Score file contains a single resource.
 
@@ -172,15 +137,6 @@ containers:
 resources:
   db:
     type: postgres
-    properties:
-      host:
-      port:
-        default: 5432
-      name:
-      username:
-        secret: true
-      password:
-        secret: true
 ```
 
 ## Service definition
diff --git a/content/en/docs/tutorials/ci-cd.md b/content/en/docs/tutorials/ci-cd.md
index bed05e9c..d7d34252 100644
--- a/content/en/docs/tutorials/ci-cd.md
+++ b/content/en/docs/tutorials/ci-cd.md
@@ -94,21 +94,6 @@ containers:
 resources:
   database:
     type: postgres
-    properties:
-      host:
-        required: true
-        default: localhost
-      port:
-        required: true
-        default: 5432
-      name:
-        required: true
-      username:
-        secret: true
-        required: false
-      password:
-        secret: true
-        required: false
 ```
 
 ## Local environment setup with Docker-Compose
diff --git a/content/en/docs/tutorials/score-compose.md b/content/en/docs/tutorials/score-compose.md
index e3d11c9d..ca13580d 100644
--- a/content/en/docs/tutorials/score-compose.md
+++ b/content/en/docs/tutorials/score-compose.md
@@ -62,16 +62,6 @@ container:
 resources:
   db:
     type: postgres
-    properties:
-      host:
-        default: localhost
-      port:
-        default: 5432
-      name:
-      username:
-        secret: true
-      password:
-        secret: true
 ```
 
 ## Executing `score-compose`