From 23574aec9c05e648408edc766205254263911c38 Mon Sep 17 00:00:00 2001
From: shikhin21 <2030677+shikhin21@users.noreply.github.com>
Date: Mon, 24 Feb 2020 02:04:11 -0500
Subject: [PATCH] docs(data): fix typo (#2409)

---
 projects/ngrx.io/content/guide/data/entity-change-tracker.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/projects/ngrx.io/content/guide/data/entity-change-tracker.md b/projects/ngrx.io/content/guide/data/entity-change-tracker.md
index 5064664a52..8012ac2b04 100644
--- a/projects/ngrx.io/content/guide/data/entity-change-tracker.md
+++ b/projects/ngrx.io/content/guide/data/entity-change-tracker.md
@@ -20,7 +20,7 @@ Many apps are easier to build when saves are "optimistic" because
 the changes are immediately available to application code that is watching collection selectors.
 The app doesn't have to wait for confirmation that the entity operation succeeded on the server.
 
-A _pessimistic save_ doesn't update the store until the server until the server confirms that the save succeeded,
+A _pessimistic save_ doesn't update the store until the server confirms that the save succeeded,
 which NgRx Data then turns into a "SUCCESS" action that updates the collection.
 With a _pessimistic_ save, the changes won't be available in the store