Merge pull request #5233 from platformsh/5232-composable-image-work---fix-link

5232 composable image work  - fix link

Author: catplat

sites/platform/src/add-services/mysql/troubleshoot.md

@@ -151,9 +151,9 @@ Behind the scenes, `max_connections` (for Professional and DG3 projects) is calc
           max_allowed_packet: 16
     ```
 
-    The memory for a given container from its `size` depends on its [container profile***](/create-apps/app-reference/single-runtime-image.md#container-profiles-cpu-and-memory).
+    The memory for a given container from its `size` depends on its [container profile](/create-apps/image-properties/size.html#container-profiles-cpu-and-memory).
 
-    For example, [MariaDB](/create-apps/app-reference/single-runtime-image.md#container-profile-reference) has a `HIGH_MEMORY` [container profile](/create-apps/app-reference/single-runtime-image.md#high_memory-container-profile).
+    For example, [MariaDB](/create-apps/image-properties/size.md#container-profile-reference) has a [`HIGH_MEMORY` container profile](/create-apps/image-properties/size.html#container-profiles-cpu-and-memory).
     For `size: L`, it means 0.40 CPU and 1280 MB of memory.
 
 If we assume the configuration above, where:

sites/platform/src/add-services/network-storage.md

@@ -206,7 +206,7 @@ and the `done` mount refers to the same directory as the `web/uploads/done` dire
 
 ## Worker instances
 
-When defining a [worker](/create-apps/app-reference/single-runtime-image.md#workers) instance,
+When defining a [worker](/create-apps/image-properties/workers.md) instance,
 keep in mind what mount behavior you want.
 
 `local` mounts are a separate storage area for each instance,

sites/platform/src/add-services/valkey.md

@@ -170,9 +170,9 @@ applications:
 
 You can define `<SERVICE_NAME>` as you like, so long as it’s unique between all defined services and matches in both the application and services configuration.
 
-The example above leverages [default endpoint](/create-apps/app-reference/single-runtime-image#relationships) configuration for relationships. That is, it uses default endpoints behind-the-scenes, providing a [relationship](/create-apps/app-reference/single-runtime-image#relationships) (the network address a service is accessible from) that is identical to the name of that service.
+The example above leverages [default endpoint](/create-apps/image-properties/relationships.md) configuration for relationships. That is, it uses default endpoints behind-the-scenes, providing a [relationship](/create-apps/image-properties/relationships.md) (the network address a service is accessible from) that is identical to the name of that service.
 
-Depending on your needs, instead of default endpoint configuration, you can use [explicit endpoint configuration](/create-apps/app-reference/single-runtime-image#relationships).
+Depending on your needs, instead of default endpoint configuration, you can use [explicit endpoint configuration](/create-apps/image-properties/relationships.md).
 
 With the above definition, the application container now has access to the service via the relationship `<SERVICE_NAME>` and its corresponding [service environment variables](/development/variables/_index.md).
 
@@ -198,10 +198,10 @@ applications:
 You can define ``<SERVICE_NAME>`` and ``<RELATIONSHIP_NAME>`` as you like, so long as it's unique between all defined services and relationships
 and matches in both the application and services configuration.
 
-The example above leverages [explicit endpoint](/create-apps/app-reference/single-runtime-image#relationships) configuration for relationships.
+The example above leverages [explicit endpoint](/create-apps/image-properties/relationships.md) configuration for relationships.
 
 Depending on your needs, instead of explicit endpoint configuration,
-you can use [default endpoint configuration](/create-apps/app-reference/single-runtime-image#relationships).
+you can use [default endpoint configuration](/create-apps/image-properties/relationships.md).
 
 With the above definition, the application container now has access to the service via the relationship `<RELATIONSHIP_NAME>` and its corresponding [service environment variables](/development/variables/_index.md).
 
@@ -344,9 +344,9 @@ relationships:
 
 You can define `<SERVICE_NAME>` as you like, so long as it’s unique between all defined services and matches in both the application and services configuration.
 
-The example above leverages [default endpoint](/create-apps/app-reference/single-runtime-image#relationships) configuration for relationships. That is, it uses default endpoints behind-the-scenes, providing a [relationship](/create-apps/app-reference/single-runtime-image#relationships) (the network address a service is accessible from) that is identical to the name of that service.
+The example above leverages [default endpoint](/create-apps/image-properties/relationships.md) configuration for relationships. That is, it uses default endpoints behind-the-scenes, providing a [relationship](/create-apps/image-properties/relationships.md) (the network address a service is accessible from) that is identical to the name of that service.
 
-Depending on your needs, instead of default endpoint configuration, you can use [explicit endpoint configuration](/create-apps/app-reference/single-runtime-image#relationships).
+Depending on your needs, instead of default endpoint configuration, you can use [explicit endpoint configuration](/create-apps/image-properties/relationships.md).
 
 With the above definition, the application container now has access to the service via the relationship `<SERVICE_NAME>` and its corresponding [`PLATFORM_RELATIONSHIPS` environment variable](/development/variables/use-variables#use-provided-variables).
 
@@ -371,10 +371,10 @@ relationships:
 You can define ``<SERVICE_NAME>`` and ``<RELATIONSHIP_NAME>`` as you like, so long as it's unique between all defined services and relationships
 and matches in both the application and services configuration.
 
-The example above leverages [explicit endpoint](/create-apps/app-reference/single-runtime-image#relationships) configuration for relationships.
+The example above leverages [explicit endpoint](/create-apps/image-properties/relationships.md) configuration for relationships.
 
 Depending on your needs, instead of explicit endpoint configuration,
-you can use [default endpoint configuration](/create-apps/app-reference/single-runtime-image#relationships).
+you can use [default endpoint configuration](/create-apps/image-properties/relationships.md).
 
 With the above definition, the application container now has access to the service via the relationship `<RELATIONSHIP_NAME>` and its corresponding [`PLATFORM_RELATIONSHIPS` environment variable](/development/variables/use-variables.md#use-provided-variables).
 

sites/platform/src/administration/cli/_index.md

@@ -210,7 +210,7 @@ eval $({{% vendor/cli %}} completion)
 
 You can use the {{% vendor/name %}} CLI to run commands on your container.
 You can use any command you've added in [dependencies](/create-apps/app-reference/single-runtime-image.md#dependencies)
-or a [hook](/create-apps/app-reference/single-runtime-image.md#hooks).
+or a [hook](/create-apps/image-properties/hooks.md).
 
 The syntax looks like the following:
 

sites/platform/src/create-apps/_index.md

@@ -15,11 +15,11 @@ keywords:
 Within a single project, you can have one or more apps and each app can have multiple instances.
 Instances are where the same code can be run with different configurations,
 such as one for external communication and one for background processes.
-Apps and instances use similar properties, with minor differences depending on the image type that you choose: 
+Apps and instances use similar properties, with minor differences depending on the image type that you choose:
 - [Single-runtime image](/create-apps/app-reference/single-runtime-image.md)
 - [Composable image](/create-apps/app-reference/composable-image.md)
 
-Not sure which image type to use? See [choosing an image type](/create-apps/app-reference.md). 
+Not sure which image type to use? See [choosing an image type](/create-apps/app-reference.md).
 
 ## A minimal application
 
@@ -88,7 +88,7 @@ Hooks are places for your custom scripts to control how your app is built and de
 ## Configure what's served
 
 Once your app is built, it needs a defined way to communicate with the outside world.
-Define its behavior with a [`web` instance](/create-apps/app-reference/single-runtime-image.md#web).
+Define its behavior with a [`web` instance](/create-apps/image-properties/web.md).
 There you can set what command runs every time your app is restarted,
 how dynamic requests are handled, and how to respond with static files.
 
@@ -123,7 +123,7 @@ Unlike other runtimes most PHP applications do not have a start command. There i
 
 {{< /note >}}
 
-The following example shows a setup for a PHP app with comments to explain the settings. 
+The following example shows a setup for a PHP app with comments to explain the settings.
 
 
 {{< codetabs >}}
@@ -191,7 +191,7 @@ web:
 <--->
 
 +++
-title=Composable image 
+title=Composable image
 +++
 
 ```yaml {configFile="app"}
@@ -258,4 +258,4 @@ myapp:
               passthru: '/app.php'
 ```
 
-{{< /codetabs >}}
+{{< /codetabs >}}