From f38bcd9ef26503640e7b624e4c887180d548f757 Mon Sep 17 00:00:00 2001
From: akshatha-harshitha
 <44336836+akshatha-harshitha@users.noreply.github.com>
Date: Tue, 23 Oct 2018 06:19:19 +0530
Subject: [PATCH] Update External Buffer Behavior.md

Missing space in heading
---
 Documentation/Documents/External Buffer Behavior.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/Documents/External Buffer Behavior.md b/Documentation/Documents/External Buffer Behavior.md
index 2136845c8390..6f4ca7c3dcce 100644
--- a/Documentation/Documents/External Buffer Behavior.md	
+++ b/Documentation/Documents/External Buffer Behavior.md	
@@ -1,4 +1,4 @@
-# ExternalBuffer in Matrix class
+# External Buffer in Matrix class
 
 There are at least 4 different implementations of the Matrix class that have over time diverged in their implementation in respect to how the external buffer case is handled. The external buffer case is when the matrix class does not actually own it's own memory and is pointing to an external buffer that is managed separately. A deviceID of MANAGEDEXTERN used to be the way this was done, however we have now moved to setting a flag m_externalBuffer in the common header to signify an eternal buffer. We have two instances of this in our code today: