From 9aebcc37a080283bdc199d7150d91f2e9bfa4e2c Mon Sep 17 00:00:00 2001
From: YoshiakiYamasaki <43057107+YoshiakiYamasaki@users.noreply.github.com>
Date: Wed, 15 May 2019 17:13:36 +0900
Subject: [PATCH] Updated README.md (#281)

There are people who think MySQL Operator can work with MySQL NDB Cluster. Update the readme to avoid confusion.
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f3ec40a51..cc51fc3b7 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # MySQL Operator
 
-The MySQL [Operator][1] creates, configures and manages MySQL clusters running on Kubernetes.
+The MySQL [Operator][1] creates, configures and manages MySQL InnoDB clusters running on Kubernetes. It is not for MySQL NDB Cluster.
 
 [![issues](https://img.shields.io/github/issues/oracle/mysql-operator.svg)](https://github.com/oracle/mysql-operator/issues)
 [![tags](https://img.shields.io/github/tag/oracle/mysql-operator.svg)](https://github.com/oracle/mysql-operator/tags)
@@ -23,7 +23,7 @@ See the [tutorial][5] which provides a quick-start guide for users of the Oracle
 
 The MySQL Operator provides the following core features:
 
-- Create and delete highly available MySQL clusters in Kubernetes with minimal effort
+- Create and delete highly available MySQL InnoDB clusters in Kubernetes with minimal effort
 - Automate database backups, failure detection, and recovery
 - Schedule automated backups as part of a cluster definition
 - Create "on-demand" backups.