From a9c30194330a14579eb0043adf762fa5aa0674b6 Mon Sep 17 00:00:00 2001
From: Neil Cuzon <58763315+NeilCuzon@users.noreply.github.com>
Date: Wed, 28 Oct 2020 00:37:35 -0700
Subject: [PATCH] Update entityRelationshipDiagram.md

---
 docs/entityRelationshipDiagram.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/entityRelationshipDiagram.md b/docs/entityRelationshipDiagram.md
index ad6508078..f18e28924 100644
--- a/docs/entityRelationshipDiagram.md
+++ b/docs/entityRelationshipDiagram.md
@@ -1,5 +1,6 @@
 # Entity Relationship Diagrams
 
+**Edit this Page** [![N|Solid](img/GitHub-Mark-32px.png)](https://github.com/mermaid-js/mermaid/blob/develop/docs/entityRelationshipDiagram.md
 > An entity–relationship model (or ER model) describes interrelated things of interest in a specific domain of knowledge. A basic ER model is composed of entity types (which classify the things of interest) and specifies relationships that can exist between entities (instances of those entity types). Wikipedia.
 
 Note that practitioners of ER modelling almost always refer to *entity types* simply as *entities*.  For example the CUSTOMER entity type would be referred to simply as the CUSTOMER entity.  This is so common it would be inadvisable to do anything else, but technically an entity is an abstract *instance* of an entity type, and this is what an ER diagram shows - abstract instances, and the relationships between them.  This is why entities are always named using singular nouns.