...

jtraband · jtraband · commit 757edbb9f3e0 · 2020-01-16T15:57:56.000-08:00
diff --git a/doc-net/controlling-serialization-4x.md b/doc-net/controlling-serialization-4x.md
@@ -5,7 +5,7 @@ redirect_from: "/doc-net/controlling-serialization.html"
 ---
 # Controlling Serialization
 
-> **NOTE: This page is for Breeze running on .NET 4.x**
+> **NOTE: This page is for Breeze running on .NET 4.x**<br>
 
 If you're serving data with Breeze-flavored ASP.NET Web API controllers, you're using the Newtonsoft.Json .NET library to serialize and de-serialize data. 
 
diff --git a/doc-net/ef-dbcontext-4x.md b/doc-net/ef-dbcontext-4x.md
@@ -4,6 +4,8 @@ redirect_from: "/old/documentation/entity-framework-dbcontext.html"
 ---
 # DbContext
 
+> **NOTE: This page is for Breeze running on .NET 4.x**<br>
+
 The Basic Breeze teaching tests make requests for data services to an ASP.NET Web API controller. The controller forwards those requests to the .NET Entity Framework (EF).
 
 This arrangement is typical for many Breeze applications and, although far from necessary, it is the arrangement we're describing in "Basic Breeze".
diff --git a/doc-net/ef-efcontextprovider-4x.md b/doc-net/ef-efcontextprovider-4x.md
@@ -5,6 +5,8 @@ redirect_from: "/doc-net/efcontextprovider.html"
 ---
 # EFContextProvider
 
+> **NOTE: This page is for Breeze running on .NET 4.x**<br>
+
 Many application servers use an ASP.NET Web API controller to handle the client's HTTP requests. And they use the Entity Framework (EF) to model and access a SQL database. Breeze has an ***EFContextProvider** component to make controller interactions with EF a little easier. It's basically a wrapper around your application's *ObjectContext* or *DbContext* that mediates between the Breeze controller and EF. It takes care of a lot of routine plumbing.
 
 You can use the EFContextProvider "as is", right out-of-the-box when you're getting started. But you will almost certainly customize it to add your application's business logic. For example, you will want to **[intercept save requests and validate them](#SaveInterception)**. You may want to do something special immediately before or after the provider tells EF to save entities to the database. And you may want to dynamically control how the provider creates the EntityFramework ObjectContext or DbContext at the core of the EF operations.
diff --git a/doc-net/persistencemanager-core.md b/doc-net/persistencemanager-core.md
@@ -3,7 +3,7 @@ layout: doc-net
 ---
 # PersistenceManager
 
-> **NOTE: This page is for Breeze running on .NET Core**<br><br>
+> **NOTE: This page is for Breeze running on .NET Core**<br>
 > [Go here for .NET 4.x version](/doc-net/contextprovider-4x)
 
 The `PersistenceManager` is a server-side component for managing data access and business validation with .NET technologies.
@@ -33,7 +33,7 @@ In `AfterSaveEntities` you have access to the entities after they've been saved
 
 You do not have to subclass a `PersistenceManager` to provide *before-* and *after-save*  logic. 
 
-You can attach handlers to the corresponding  delegate properties of a `ContextProvider` instance: `BeforeSaveEntityDelegate`, `BeforeSaveEntitiesDelegate` and `AfterSaveEntitiesDelegate`. There is no difference in functionality. Choose the approach that suits your architectural style.
+You can attach handlers to the corresponding  delegate properties of a `PersistenceManager` instance: `BeforeSaveEntityDelegate`, `BeforeSaveEntitiesDelegate` and `AfterSaveEntitiesDelegate`. There is no difference in functionality. Choose the approach that suits your architectural style.
 
 Each of these methods receives entity change information in the form of an `EntityInfo`. 
 
@@ -45,11 +45,11 @@ The `SaveChanges` method translates the incoming JSON change-set (aka "SaveBundl
 
 An `EntityInfo` describes the entity-to-be-saved and the save operation to be performed on it. Here is its annotated interface:
 
-    // A back reference to the concrete ContextProvider that created it
-    ContextProvider ContextProvider { get; internal set; }
+    // A back reference to the concrete PersistenceManager that created it
+    PersistenceManager ContextProvider { get; internal set; }
 
     // The values to save represented as an instance of a .NET class
-    // Created for you by the ContextProvider
+    // Created for you by the PersistenceManager
     Object Entity { get; internal set; }
 
     // Whether the entity is to be added, updated, or deleted
diff --git a/doc-net/webapi-controller-core.md b/doc-net/webapi-controller-core.md
@@ -3,8 +3,7 @@ layout: doc-net
 ---
 # The ASP.NET Web API controller
 
-> **NOTE: This page is for Breeze running on .NET Core**
-
+> **NOTE: This page is for Breeze running on .NET Core**<br>
 > [Go here for .NET 4.x version](/doc-net/webapi-controller-4x)
 
 The Basic Breeze teaching tests in the [DocCode sample](/doc-samples/doccode "Breeze 'DocCode' teaching sample") demonstrate the Breeze `EntityManager` making requests of a **Breeze ASP.NET Web API controller**.
diff --git a/doc-net/webapi-routing-4x.md b/doc-net/webapi-routing-4x.md
@@ -5,8 +5,7 @@ redirect_from: "/doc-net/webapi-routing.html"
 ---
 # Web API Routing
 
-> **NOTE: This page is for Breeze running on .NET 4.x**
-
+> **NOTE: This page is for Breeze running on .NET 4.x**<br>
 > [Go here for .NET Core version](/doc-net/webapi-controller-core)
 
 We've built a Breeze controller that Web API will discover automatically. Now we must teach the Web API to route Breeze client requests to this controller and configure the Web API to use the controller properly.
