Merge pull request #39 from exdx/docs-readme-2

docs: Further update provider docs

README.md

@@ -8,9 +8,8 @@ Containers are great tools that can encapsulate an application and its dependenc
 allowing apps to run anywhere in a streamlined way. Some container images contain
 commands to start a long-lived binary, whereas others may simply contain data
 that needs to be available in the environment (for example, a Kubernetes cluster).
-For example, [operator-framework bundles](https://olm.operatorframework.io/docs/tasks/creating-operator-bundle/) and [crossplane packages](https://crossplane.io/docs/v1.9/concepts/packages.html) are examples of using
-container images to store manifests, which can be unpacked on-cluster and made
-available to end users.
+For example, [operator-framework bundles](https://olm.operatorframework.io/docs/tasks/creating-operator-bundle/) and [crossplane packages](https://crossplane.io/docs/v1.9/concepts/packages.html) both use
+container images to store Kubernetes manifests. These manifests are unpacked on-cluster and made available to end users.
 
 One of the downsides of using container images to store data is that they are
 necessarily opaque. There's no way to quickly tell what's inside the image, although