diff --git a/design/vela-core/appfile-design.md b/design/vela-core/appfile-design.md index 4990e7e21..f3674c11a 100644 --- a/design/vela-core/appfile-design.md +++ b/design/vela-core/appfile-design.md @@ -72,7 +72,7 @@ It will build container image, render deployment manifests in yaml, and apply th ### Extensible Design -The Appfile could be extended with more configurations by adding more capabilities to the OAM system. The config fields in Appfile are strongly correlated to the [capabilities system of OAM](https://github.com/oam-dev/kubevela/blob/master/docs/design.md#2-capability-oriented-architecture) – Config fields are registered in the capabilities system and exposed via a [CUE template](https://cuelang.org/). +The Appfile could be extended with more configurations by adding more capabilities to the OAM system. The config fields in Appfile are strongly correlated to the [capabilities system of OAM](../../docs/en/design.md#capability-oriented) – Config fields are registered in the capabilities system and exposed via a [CUE template](https://cuelang.org/). Here is an example of a capability definition that platform builders register: @@ -140,7 +140,7 @@ In the following, we will discuss technical details of the proposed design. ### Registration via Definition/Capability -Vela allows platform builders to extend Appfile config fields by registering them via [capabilities system of OAM](https://github.com/oam-dev/kubevela/blob/master/docs/design.md#2-capability-oriented-architecture). +Vela allows platform builders to extend Appfile config fields by registering them via [capabilities system of OAM](../../docs/en/design.md#capability-oriented). The entire template should be put under `spec.extension.template` as raw string: diff --git a/docs/en/developers/learn-appfile.md b/docs/en/developers/learn-appfile.md index 12add1b6e..42c1edb58 100644 --- a/docs/en/developers/learn-appfile.md +++ b/docs/en/developers/learn-appfile.md @@ -147,7 +147,7 @@ spec: ## [Optional] Configure another workload type -By now we have deployed a *[Web Service](references/workload-types/web-service.md)*, which is the default workload type in KubeVela. We can also add another service of *[Task](references/workload-types/task.md)* type in the same app: +By now we have deployed a *[Web Service](references/workload-types/webservice.md)*, which is the default workload type in KubeVela. We can also add another service of *[Task](references/workload-types/task.md)* type in the same app: ```yaml services: