Resolving comments for the Basic Concepts section. Aggregate Mirror c…

…oncept added.

concepts/aggregate-mirror.md

@@ -0,0 +1,10 @@
+---
+title: Aggregate Mirror 
+headline: Aggregate Mirror
+bodyclass: docs
+layout: docs
+sidenav: doc-side-concepts-nav.html
+type: markdown
+---
+<h2 class="top">Aggregate Mirror</h2> 
+Aggregate Mirror contains the latest state of an Aggregate. It “reflects” how it ”looks” at the time of the last update.

concepts/bounded-context.md

@@ -11,7 +11,7 @@ type: markdown
 Bounded Context is an autonomous component with its own domain model and its own Ubiquitous Language. 
 Large systems usually have multiple Bounded Contexts. 
 
-For example, you can consider orders, user management, shipping as examples of the separate contexts within online retail system. 
+For example, you can consider `Orders`, `User management`, `Shipping` as examples of the separate contexts within online retail system. 
 
 In Spine, interaction between Bounded Contexts is organized using Integration Events.
 

concepts/command.md

@@ -8,9 +8,7 @@ type: markdown
 ---
 <h2 class="top">Command</h2> 
 
-Commands are messages that instruct an entity within Spine framework to perform a certain action. Compared with events, command is not a statement of fact. They are a request, and, thus, can be refused. 
-
-A typical way to convey refusal is to throw an error or failure. 
+Commands are messages that instruct an entity within Spine framework to perform a certain action. Compared with events, command is not a statement of fact. They are a request, and, thus, can be refused. A typical way to convey refusal is to throw an error or rejection. 
 
 In Spine, commands are defined as a Protocol buffer messages.
 

concepts/event.md

@@ -10,4 +10,4 @@ type: markdown
 
 Event is something that happened in the past. All changes to an application state are captured as a sequence of events. Events are the main “database” of the application. 
 
-In Spine, events are defined as Protocol buffer messages. 
+In Spine, events are defined as Protobuf messages. 

concepts/identifier.md

@@ -15,4 +15,4 @@ Spine framework supports the following types of identifiers:
 * String,
 * A generated Java class implementing the `Message`.
 
-We recommend you to select Identifiers for your IDs and encourage using message-based IDs to to make your API `strongly pronounced` and `type-safe`. 
+We recommend you to select Identifiers for your IDs and encourage using message-based IDs to to make your API strongly pronounced and type-safe. 

concepts/index.md

@@ -15,7 +15,6 @@ We assume that you are familiar with the basics of Domain-Driven Design.
 
 Below you can find a typical Spine Event Engine application architecture; its building blocks are also described below.
 
-To be added: Spine Event engine architecture overview.
 
 
 

concepts/rejection.md

@@ -9,10 +9,8 @@ type: markdown
 <h2 class="top">Rejection</h2> 
 
 Rejection is a state of business logic which can be handled by the end user. 
-Consider the following examples of rejections: 
-* “credit card validation declined”, 
-* “order cannot be empty”, 
-* “insufficient funds”.
-
-In Spine, rejections are defined as Protocol buffer messages. 
+In Spine, rejections are defined as Protocol buffer messages. Consider the following examples of rejections: 
+* `CreditCardValidationDecllined`, 
+* `OrderCannotBeEmpty`, 
+* `InsufficientFunds`.
 

concepts/snapshot.md

@@ -8,5 +8,6 @@ type: markdown
 ---
 <h2 class="top">Snapshot</h2> 
 
-Snapshot is a state of an Aggregate. A snapshot ”sits” in between events in the history, so that you do not have to replay them all. 
-You read events backwards until you encounter a snapshot, then apply it to the Aggregate, and then play trailing events.
+Snapshot is a state of an Aggregate. A snapshot ”sits” in between events in the history.
+
+`AggregateStorage` reads events backwards until encounters a snapshot, applies it to the Aggregate, and plays trailing events.

concepts/stand.md

@@ -8,5 +8,4 @@ type: markdown
 ---
 <h2 class="top">Stand</h2> 
 
-Stand provides the latest states of Aggregates. It may return a complete state or its fragment (if the query requests only partial representation).
-
+Stand is a read-side API façade of a BoundedContext.