From 412d7355ea02fcbe33a591d199c03880b3e35023 Mon Sep 17 00:00:00 2001
From: Dan Kohn <dan@linuxfoundation.org>
Date: Fri, 9 Feb 2018 17:33:22 -0500
Subject: [PATCH] Update Certified Kubernetes logo

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

diff --git a/docs/design/design_v1.8.md b/docs/design/design_v1.8.md
index 5a8792ff..4341cc79 100644
--- a/docs/design/design_v1.8.md
+++ b/docs/design/design_v1.8.md
@@ -1,6 +1,6 @@
 ## Implementation design for kubeadm
 
-<img src="https://raw.githubusercontent.com/cncf/artwork/master/kubernetes/certified-kubernetes/1.8/color/certified_kubernetes_1.8_color.png" align="right" width="150px">`kubeadm init` and `kubeadm join` together provides a nice user experience for creating a best-practice but bare Kubernetes cluster from scratch.
+<img src="https://raw.githubusercontent.com/cncf/artwork/master/kubernetes/certified-kubernetes/1.8/color/certified-kubernetes-1.8-color.png" align="right" width="150px">`kubeadm init` and `kubeadm join` together provides a nice user experience for creating a best-practice but bare Kubernetes cluster from scratch.
 However, it might not be obvious _how_ kubeadm does that.
 
 This document strives to explain the phases of work that happen under the hood.