@genesislcap/foundation-layout 14.120.3-alpha-7ba1ef7.0 → 14.121.1

package/README.md

@@ -183,7 +183,7 @@ Use this function over `.layoutRequiredRegistrations(layout: SerialisedLayout)`
 
 ### Serialising layout
 
-The JavaScript API can be used to manually save and load layout states. This only describes the state of the dynamic layout itself. It is the responsibility of any components contained within their layout to serialise their own state, if required.
+The JavaScript API can be used to manually save and load layout states. This only describes the state of the dynamic layout itself. It is the responsibility of each component within the layout to serialise its own state, if required.
 To enable autosaving the layout see [here](#autosaving-layout).
 
 #### [Get Layout](./docs/api/foundation-layout.foundationlayout.getlayout.md)
@@ -274,7 +274,7 @@ This section concerns the behaviour of elements inside the layout. If you are us
 
 ### Element lifecycle (gating)
 
-Some actions that the user can perform with items in the layout which will run the component lifecycle functions (`connectedCallback` and `disconnectedCallback`) at times when you don't want them to run:
+Some actions that the user can perform with items in the layout will run the component lifecycle functions (`connectedCallback` and `disconnectedCallback`) when you don't want them to run:
 - when an item is dragged around the layout
 - potentially, when another item is removed from the layout
 - potentially, when new items are added to the layout
@@ -304,14 +304,14 @@ Throughout Foundation UI, there is no need to de-register a component that is re
 
 ### Managing the state
 
-Items inside the layout can save and restore state using various methods, but it can become difficult to manage the state if you're adding the same item to the layout multiple times (multiple instances of the same web component).
+Items inside the layout can save and restore the state using various methods, but it can become difficult to manage the state if you're adding the same item to the layout multiple times (multiple instances of the same web component).
 
-You can implement the [LayoutComponentWithState](./docs/api/foundation-layout.layoutcomponentwithstate.md) interface which enables you to save and load the state *per instance* of your components. See the linked interface and the associated functions API documentation for examples and explanations of usage.
+You can implement the [LayoutComponentWithState](./docs/api/foundation-layout.layoutcomponentwithstate.md) interface, which enables you to save and load the state *per instance* of your components. See the linked interface and the associated functions API documentation for examples and explanations of usage.
 
-Usage of this interface is optional, if you do not need to manage the state for your components in this way then simply do not implement the interface.
+Usage of this interface is optional; if you do not need to manage the state for your components in this way, then simply do not implement the interface.
 
 :::warning
-The layout system is only interacting with the immediately contained items - so if you have components that contain other components, the top-level components will need to interact with the contained components to manage their state.
+The layout system is only interacting with the immediately contained items - so if you have components that contain other components, each top-level component must interact with the contained components to manage their states.
 :::
 
 :::danger
@@ -328,8 +328,8 @@ There are certain limitations to this function, especially when using custom ele
 As a general rule, if you need to have elements with FAST bindings inside the layout, wrap them in custom elements.
 :::
 
-If you are writing your own custom element which needs to work inside of the layout, follow these steps.
-In the `@genesislcap/foundation-utils` package, there is a mix-in class `LifecycleMixin` which overrides the `cloneNode` API.
+If you are writing your own custom element that needs to work inside the layout, follow these steps.
+In the `@genesislcap/foundation-utils` package, there is a mix-in class `LifecycleMixin`, which overrides the `cloneNode` API.
 
 ```typescript
 // Make a call to `deepClone` and manually clone children

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@genesislcap/foundation-layout",
   "description": "Genesis Foundation UI App Layout",
-  "version": "14.120.3-alpha-7ba1ef7.0",
+  "version": "14.121.1",
   "license": "SEE LICENSE IN license.txt",
   "main": "dist/esm/index.js",
   "types": "dist/foundation-layout.d.ts",
@@ -27,15 +27,15 @@
     "test:debug": "genx test --debug"
   },
   "devDependencies": {
-    "@genesislcap/foundation-testing": "14.120.3-alpha-7ba1ef7.0",
-    "@genesislcap/genx": "14.120.3-alpha-7ba1ef7.0",
+    "@genesislcap/foundation-testing": "14.121.1",
+    "@genesislcap/genx": "14.121.1",
     "rimraf": "^3.0.2"
   },
   "dependencies": {
     "@genesis-community/golden-layout": "^2.11.0",
-    "@genesislcap/foundation-comms": "14.120.3-alpha-7ba1ef7.0",
-    "@genesislcap/foundation-logger": "14.120.3-alpha-7ba1ef7.0",
-    "@genesislcap/foundation-utils": "14.120.3-alpha-7ba1ef7.0",
+    "@genesislcap/foundation-comms": "14.121.1",
+    "@genesislcap/foundation-logger": "14.121.1",
+    "@genesislcap/foundation-utils": "14.121.1",
     "@microsoft/fast-components": "^2.21.3",
     "@microsoft/fast-element": "^1.7.0",
     "@microsoft/fast-foundation": "^2.33.2",
@@ -50,5 +50,5 @@
     "access": "public"
   },
   "customElements": "dist/custom-elements.json",
-  "gitHead": "f77f47498e0833672401df009209b294e077843d"
+  "gitHead": "8e78bf8e11be74bf258060aedab854dea1c7e11b"
 }