From 0266d6e3d623f12794b9f540239958dbc4934e79 Mon Sep 17 00:00:00 2001 From: "rick.parker" Date: Wed, 5 Oct 2016 11:46:40 +0100 Subject: [PATCH] Fix typo in persistence docs. --- docs/source/persistence.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/persistence.rst b/docs/source/persistence.rst index e40e02f3fe..3abe759045 100644 --- a/docs/source/persistence.rst +++ b/docs/source/persistence.rst @@ -51,7 +51,7 @@ later version of a schema or even provide a ``MappedSchema`` not originally offe It is expected that multiple different contract state implementations might provide mappings to some common schema. For example an Interest Rate Swap contract and an Equity OTC Option contract might both provide a mapping to a common Derivative schema. The schemas should typically not be part of the contract itself and should exist independently of it -to encourage re-use of a common set within a particular buisness area or Cordapp. +to encourage re-use of a common set within a particular business area or Cordapp. ``MappedSchema`` offer a family name that is disambiguated using Java package style name-spacing derived from the class name of a *schema family* class that is constant across versions, allowing the ``SchemaService`` to select a preferred version