new git resource

mattmakai · mattmakai · commit 0ff8428b2d39 · 2020-11-29T10:55:58.000-05:00
diff --git a/content/pages/02-development-environments/19-git.markdown b/content/pages/02-development-environments/19-git.markdown
@@ -223,6 +223,11 @@ workflow. These resources will come in handy for specific Git subjects.
   system. This is an awesome read to get a view on how Git works under the
   commands you're using to manipulate these objects.
 
+* [How to Undo Mistakes With Git Using the Command Line](https://www.youtube.com/watch?v=lX9hsdsAeTk)
+  is a video that covers topics like resetting a file to an old revision,
+  recovering deleted commits, squashing multiple commits into one with 
+  interactive rebase and recovering deleted branches.
+
 
 ## Git Workflows
 Teams of developers can use Git in varying workflows because of Git's 
diff --git a/content/pages/10-working/01-event-streams.markdown b/content/pages/10-working/01-event-streams.markdown
@@ -19,15 +19,18 @@ streams. Amazon Web Services' Kinesis and
 are proprietary hosted implementations.
 
 
-## How are event streams stored?
+## How are event streams typically stored?
 Some applications, such as aggregating millions of sensors, or thousands
-of constantly streaming cameras, throw off large amounts of data. It's
-difficult to process those large volumes of data in traditional data stores,
-so event streams are built off of a simpler data structure: logs. 
+of streaming cameras, constantly output large amounts of data with no breaks. 
+It is difficult to process such large volumes of data in traditional data 
+stores, so event streams are built off of a simpler data structure: logs. 
 
-Logs are ordered sequences of events and they typically have less constraints 
-than a database. Logs can handle the high throughput writes needed to keep 
-up with the constant flood of data from the source of an event stream.
+Logs are ordered sequences of events and they typically have less constraints
+than a database. In event streams, logs are also immutable. They do not change
+once they are written. Instead, newer events are written in the sequence as
+state changes. The reduced constraints compared to a database and the
+immutability mean that logs can handle the high throughput writes needed to
+keep up with the constant flood of data from the source of an event stream.
 
 
 ## Event stream resources
@@ -36,4 +39,5 @@ up with the constant flood of data from the source of an event stream.
   concepts behind event streams and how they fit into 
   [microservices](/microservices.html) architectures.
 
-
+* Quora has a solid answer to the question of 
+  [what is an event stream?](https://www.quora.com/What-is-an-event-stream).
