Fix links to devfile.io

docs/website/docs/command-reference/deploy.md

@@ -11,7 +11,7 @@ The kind `deploy` is supported by the devfile format starting from version 2.2.0
 
 The `deploy` command is typically a *composite* command, composed of several *apply* commands:
 - a command referencing an `image` component that, when applied, will build the image of the container to deploy, and push it to its registry,
-- a command referencing a [`kubernetes` component](https://devfile.io/docs/devfile/2.2.0/user-guide/adding-a-kubernetes-or-openshift-component-to-a-devfile) that, when applied, will create a Kubernetes resource in the cluster.
+- a command referencing a [`kubernetes` component](https://devfile.io/docs/2.2.0-alpha/defining-kubernetes-resources) that, when applied, will create a Kubernetes resource in the cluster.
 
 With the following example `devfile.yaml` file, a container image will be built by using the `Dockerfile` present in the directory,
 the image will be pushed to its registry and a Kubernetes Deployment will be created in the cluster, using this freshly built image.

docs/website/docs/command-reference/dev.md

@@ -239,7 +239,7 @@ These instructions make up the development cycle of `odo dev`.
 
 With the following example `devfile.yaml` file generated by `odo init` and selecting `nodejs`, a container image will be pushed to the cluster, as well as your source code in order to start the development inner loop cycle.
 
-A much more descriptive explanation on each part of a Devfile can be found on the [Devfile API reference](https://devfile.io/docs/devfile/2.0.0/user-guide/api-reference/) site.
+A much more descriptive explanation on each part of a Devfile can be found on the [Devfile API reference](https://devfile.io/docs/2.2.0-alpha/devfile-schema) site.
 
 Below, we'll explain each section of the corresponding Devfile:
 

docs/website/docs/development/devfile.md

@@ -7,7 +7,7 @@ sidebar_position: 30
 
 ### Overview
 
-We use the latest [Devfile 2.2.0 reference](https://devfile.io/docs/devfile/2.2.0/user-guide/api-reference/) in `odo`.
+We use the latest [Devfile 2.2.0 reference](https://devfile.io/docs/2.2.0-alpha/devfile-schema) in `odo`.
 
 Below are `odo`-specific examples regarding the Devfile reference. Everything we have listed below is implemented in the current version of `odo`.
 
@@ -98,7 +98,7 @@ We use practical approach outlining the details of Devfile. The example is a mod
 
 In this example, we are deploying a full Node.js application that is available through both `odo dev` and `odo deploy`. 
 
-For a more in-depth detailed outline of Devfile, please refer to the official [Devfile 2.2.0 reference](https://devfile.io/docs/devfile/2.2.0/user-guide/api-reference/).
+For a more in-depth detailed outline of Devfile, please refer to the official [Devfile 2.2.0 reference](https://devfile.io/docs/2.2.0-alpha/devfile-schema).
 
 **NOTE:** Some portions of the Devfile examples are commented out to show what is *available* but it does not apply to the practical example.
 
@@ -686,7 +686,7 @@ components:
 ### Not Yet Implemented
 
 
-All full descriptions of missing specification features can be found on the [2.2.0 API Specification](https://devfile.io/docs/devfile/2.2.0/user-guide/api-reference/).
+All full descriptions of missing specification features can be found on the [2.2.0 API Specification](https://devfile.io/docs/2.2.0-alpha/devfile-schema).
 
 List of Devfile spec features not yet implemented in `odo`:
 
@@ -737,7 +737,7 @@ components:
 - name: outerloop-deployment
   kubernetes:
     # NOT YET IMPLEMENTED
-    # See: https://devfile.io/docs/devfile/2.2.0/user-guide/api-reference/
+    # See: https://devfile.io/docs/2.2.0-alpha/devfile-schema
     # for full details
     # endpoints:
 

docs/website/versioned_docs/version-2.5.0/command-reference/deploy.md

@@ -12,7 +12,7 @@ The kind `deploy` is supported by the devfile format starting from version 2.2.0
 
 The `deploy` command is typically a *composite* command, composed of several *apply* commands:
 - a command referencing an `image` component that, when applied, will build the image of the container to deploy, and push it to its registry,
-- a command referencing a [`kubernetes` component](https://devfile.io/docs/devfile/2.2.0/user-guide/adding-kubernetes-component-to-a-devfile.html) that, when applied, will create a Kubernetes resource in the cluster.
+- a command referencing a [`kubernetes` component](https://devfile.io/docs/2.2.0-alpha/defining-kubernetes-resources) that, when applied, will create a Kubernetes resource in the cluster.
 
 With the following example `devfile.yaml` file, a container image will be built by using the `Dockerfile` present in the directory,
 the image will be pushed to its registry and a Kubernetes Deployment will be created in the cluster, using this freshly built image.