Move logos into their own directory

Signed-off-by: timflannagan <[email protected]>

Author: timflannagan

README.md

@@ -1,5 +1,5 @@
-<img src="/logo.svg#gh-light-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
-<img src="/logo-dark-mode.svg#gh-dark-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
+<img src="logo/logo.svg#gh-light-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
+<img src="logo/logo-dark-mode.svg#gh-dark-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
 
 [![Container Repository on Quay.io](https://quay.io/repository/operator-framework/olm/status "Container Repository on Quay.io")](https://quay.io/repository/operator-framework/olm)
 [![License](http://img.shields.io/:license-apache-blue.svg)](http://www.apache.org/licenses/LICENSE-2.0.html)
@@ -10,7 +10,6 @@
 
 User documentation can be found on the [OLM website][olm-docs].
 
-
 ## Overview
 
 This project is a component of the [Operator Framework](https://github.com/operator-framework), an open source toolkit to manage Kubernetes native applications, called Operators, in an effective, automated, and scalable way. Read more in the [introduction blog post](https://operatorhub.io/what-is-an-operator) and learn about practical use cases at the [OLM website][olm-docs].
@@ -97,7 +96,7 @@ Learn more about the components used by OLM by reading about the [architecture]
 
 OLM standardizes interactions with operators by requiring that the interface to an operator be via the Kubernetes API. Because we expect users to define the interfaces to their applications, OLM currently uses CRDs to define the Kubernetes API interactions.
 
-Examples: [EtcdCluster CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdclusters.etcd.database.coreos.com.crd.yaml), 
+Examples: [EtcdCluster CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdclusters.etcd.database.coreos.com.crd.yaml),
 [EtcdBackup CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdbackups.etcd.database.coreos.com.crd.yaml)
 
 ## Descriptors
@@ -112,10 +111,10 @@ To minimize the effort required to run an application on kubernetes, OLM handles
 
 This is achieved through additional metadata on the application definition. Each operator must define:
 
- - The CRDs that it is responsible for managing.
-   - e.g., the etcd operator manages `EtcdCluster`.
- - The CRDs that it depends on.
-   - e.g., the vault operator depends on `EtcdCluster`, because Vault is backed by etcd.
+- The CRDs that it is responsible for managing.
+  - e.g., the etcd operator manages `EtcdCluster`.
+- The CRDs that it depends on.
+  - e.g., the vault operator depends on `EtcdCluster`, because Vault is backed by etcd.
 
 Basic dependency resolution is then possible by finding, for each “required” CRD, the corresponding operator that manages it and installing it as well. Dependency resolution can be further constrained by the way a user interacts with catalogs.
 

logo/README.md

@@ -0,0 +1,3 @@
+# Logo
+
+Home for the OLM related logos.