From 4cb42e0d8f602971798b48120542308775559b76 Mon Sep 17 00:00:00 2001
From: Preankhan Gowrypalan <38509853+Preankhan@users.noreply.github.com>
Date: Mon, 5 Nov 2018 20:53:43 +0000
Subject: [PATCH] Grammar (#21127)

* Grammar

Removed unnecessary use of 'undemand' in a sentence.

* Update index.md
---
 guide/english/developer-ethics/the-programmers-oath/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/english/developer-ethics/the-programmers-oath/index.md b/guide/english/developer-ethics/the-programmers-oath/index.md
index 11f92a0d77..bf89881f38 100644
--- a/guide/english/developer-ethics/the-programmers-oath/index.md
+++ b/guide/english/developer-ethics/the-programmers-oath/index.md
@@ -39,7 +39,7 @@ Notice that in the promise, there is an aspect of both "behavior" and "structure
 ### Promise 3
 >3. I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.
 
-Customers, users, and even businesses would expect that we would be able to undemand prove that our code works as it is supposed to. Notice that in the oath there are words like quick, sure, and repeatable. You want to be able to prove on a moment's notice that code still works as it is supposed to.
+Customers, users, and even businesses would expect that we would be able to prove that our code works as it is supposed to. Notice that in the oath there are words like quick, sure, and repeatable. You want to be able to prove on a moment's notice that code still works as it is supposed to.
 
 If you add a new feature, that doesn't break anything older, or fix a new structure that doesn't break anything that used to be there, you want to be able to show that quickly and easily, that the code still does what it's intended to do.