docs/8.0/ayanova/docs/svc-workorders.md

@@ -12,7 +12,7 @@ If you are just getting started with AyaNova, we have a [help page](svc-workorde
 
 A work order in AyaNova is a tree-like structure with a Header section at the top and a collection of one or more work order items below the header.
 
-Each work order item in turn can optionally contain any one of 9 different types of service related "grand child" objects such as collections of zero or more Parts, zero or more Labor items etc.
+Each work order item in turn can optionally contain any of 10 different types of service related "grand child" objects such as collections of zero or more Parts, zero or more Labor items etc.
 
 The work order interface is designed so that different types of items can be added if required or left out if not used. For example, if you do not have Expenses or Travel to track they can be left out and will not appear anywhere on the work order.
 
@@ -82,7 +82,7 @@ Only parts that were previously consumed on a work order but unusued and later r
 
 Limited access roles have further special restrictions to limit what they can see and interact with to the minimum required to do their job:
 
-- No access to the `Service` navigation pane items so they will only be able to open work orders from their [personal schedule](home-schedule.md) form
+- No access to the `Service` navigation pane items so they will only be able to see and open work orders from their [personal schedule](home-schedule.md) form
 - No access to any work order items where _they_ are not one of the selected Scheduled users
 - No or partial only access to specific areas of the work order form (in the table below)
 
@@ -156,7 +156,9 @@ This pattern is used for all the collections below the header so that the simple
 
 #### What if I don't need Loaners or Tasks or Expenses or ...?
 
-The grand child sections of a work order are **optional**, designed to work around the User as needed but get out of the way if not needed, so they won't be displayed until one of that type of object is added from the [Work order Items context menu](#work-order-item-context-menu) so there is generally no need to completely remove a section however you might not want it to even be _offered_ as an option in the Work order item's Add context menu section to avoid any confusion or prevent Users from accidentally using that feature.
+The grand child sections of a work order are **optional**, designed to work around the User as needed but get out of the way if not needed, so they won't be displayed until one of that type of object is added from the [Work order Items context menu](#work-order-item-context-menu).
+
+There is generally no need to completely remove a section however you might not want it to even be _offered_ as an option in the Work order item's Add context menu section to avoid any confusion or prevent Users from accidentally using that feature.
 
 Unwanted sections can be completely removed as an option by [customizing](ay-customize.md) the work order form and un-checking the _Visible_ checkbox for those grand child collections: