From 691c5c1cc2d8a300813ff26f835e27ecb6244978 Mon Sep 17 00:00:00 2001 From: Tom Cowland Date: Wed, 15 Nov 2023 10:19:18 +0000 Subject: [PATCH] fixup! [Docs] Add Juypyter notebook covering version workflows Co-authored-by: David Feltell <7827094+feltech@users.noreply.github.com> Signed-off-by: Tom Cowland --- examples/versioning.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/versioning.ipynb b/examples/versioning.ipynb index 10394a8..d7e19a9 100644 --- a/examples/versioning.ipynb +++ b/examples/versioning.ipynb @@ -346,7 +346,7 @@ "source": [ "It was noted earlier that Hosts, generally speaking, should never \"string munge\" an existing entity reference to derive another one as this makes assumptions about how any manager may work. This is guaranteed to be different for each manager. \n", "\n", - "Entity references shold be considerd \"opaque handles\", and instead use the appropriate API methods to achieve the same end.\n", + "Entity references should be considerd \"opaque handles\", and instead use the appropriate API methods to achieve the same end.\n", "\n", "We can use the `EntityVersionsRelationshipSpecification` from the `specifications.lifecycle` module, which defines a well-known relationship trait set for querying different versions of the same entity using the `getWithRelationship` method:" ]