From b0498c82edbc11bc66ea7a134d79737174555e36 Mon Sep 17 00:00:00 2001
From: Karel Piwko <kpiwko@redhat.com>
Date: Thu, 21 May 2020 15:29:50 +0200
Subject: [PATCH] chore: fixed a typo in bundle manifest format

---
 docs/design/operator-bundle.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/design/operator-bundle.md b/docs/design/operator-bundle.md
index 0f351af92..fe5d05433 100644
--- a/docs/design/operator-bundle.md
+++ b/docs/design/operator-bundle.md
@@ -17,7 +17,7 @@ An `Operator Bundle` is built as a scratch (non-runnable) container image that c
 
 ### Bundle Manifest Format
 
-The standard bundle format requires two directories named `manifests` and `metatdata`. The `manifests` directory is where all operator manifests are resided including ClusterServiceVersion (CSV), CustomResourceDefinition (CRD) and other supported Kubernetes types. The `metadata` directory is where operator metadata is located including `annotations.yaml` which contains additional information such as package name, channels and media type. Also, `dependencies.yaml` which contains the operator dependency information can be included in `metadata` directory.
+The standard bundle format requires two directories named `manifests` and `metadata`. The `manifests` directory is where all operator manifests are resided including ClusterServiceVersion (CSV), CustomResourceDefinition (CRD) and other supported Kubernetes types. The `metadata` directory is where operator metadata is located including `annotations.yaml` which contains additional information such as package name, channels and media type. Also, `dependencies.yaml` which contains the operator dependency information can be included in `metadata` directory.
 
 Below is the directory layout of an operator bundle inside a bundle image:
 ```bash