@@ -6,7 +6,7 @@ weight: 200
6
6
---
7
7
8
8
A _ Configuration_ package is an
9
- [ OCI container images ] ( https://opencontainers.org/ ) containing a collection of
9
+ [ OCI container image ] ( https://opencontainers.org/ ) containing a collection of
10
10
[ Compositions] ({{<ref "./compositions" >}}),
11
11
[ Composite Resource Definitions] ({{<ref "./composite-resource-definitions" >}})
12
12
and any required [ Providers] ({{<ref "./providers">}}) or
@@ -43,7 +43,7 @@ registry with the `--registry` flag on the [Crossplane pod]({{<ref "./pods">}})
43
43
{{< /hint >}}
44
44
45
45
For example to install the
46
- [ Upbound AWS reference platform] ( https://marketplace.upbound.io/configurations/upbound/platform-ref-aws/v0.6.0 ) ,
46
+ [ Upbound AWS reference platform] ( https://marketplace.upbound.io/configurations/upbound/platform-ref-aws/v0.6.0 ) .
47
47
48
48
``` yaml {label="install"}
49
49
apiVersion : pkg.crossplane.io/v1
@@ -78,7 +78,7 @@ crossplane-stable/crossplane \
78
78
79
79
# ## Install offline
80
80
81
- Installing Crossplane packages offline requires a local container registry like
81
+ Installing Crossplane packages offline requires a local container registry, such as
82
82
[Harbor](https://goharbor.io/) to host the packages. Crossplane only
83
83
supports installing packages from a container registry.
84
84
@@ -437,7 +437,7 @@ Including YAML files that aren't Compositions or CompositeResourceDefinitions,
437
437
including Claims isn't supported.
438
438
{{</hint >}}
439
439
440
- By default, Crossplane creates an `.xpkg` file of the Configuration name and
440
+ By default, Crossplane creates a `.xpkg` file of the Configuration name and
441
441
a SHA-256 hash of the package contents.
442
442
443
443
For example, a {{<hover label="xpkgName" line="2">}}Configuration{{</hover>}}
0 commit comments