Add providesApis and consumesApis to component spec

docs/features/software-catalog/descriptor-format.md

@@ -381,7 +381,7 @@ spec:
   type: website
   lifecycle: production
   owner: artist-relations@example.com
-  implementsApis:
+  providesApis:
     - artist-api
 ```
 
@@ -451,6 +451,25 @@ is optional.
 The software catalog expects a list of one or more strings that references the
 names of other entities of the `kind` `API`.
 
+This field has the same behavior as `spec.providesApis` and will be deprecated
+in the future.
+
+### `spec.providesApis` [optional]
+
+Links APIs that are provided by the component, e.g. `artist-api`. This field is
+optional.
+
+The software catalog expects a list of one or more strings that references the
+names of other entities of the `kind` `API`.
+
+### `spec.consumesApis` [optional]
+
+Links APIs that are consumed by the component, e.g. `artist-api`. This field is
+optional.
+
+The software catalog expects a list of one or more strings that references the
+names of other entities of the `kind` `API`.
+
 ## Kind: Template
 
 Describes the following entity kind:

docs/features/software-catalog/references.md

@@ -51,7 +51,7 @@ spec:
   type: service
   lifecycle: experimental
   owner: group:pet-managers
-  implementsApis:
+  providesApis:
     - petstore
     - internal/streetlights
     - hello-world
@@ -66,7 +66,7 @@ catalog that is of kind `Group`, namespace `default` (which, actually, also can
 be left out in its own yaml file because that's the default value there too),
 and name `pet-managers`.
 
-The entries in `implementsApis` are also references. In this case, none of them
+The entries in `providesApis` are also references. In this case, none of them
 needs to specify a kind since we know from the context that that's the only kind
 that's supported here. The second entry specifies a namespace but the other ones
 don't, and in this context, the default is to refer to the same namespace as the