diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 0b3c61b9..bec46cd7 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -1327,23 +1327,23 @@ BUILD 115
 	i.e. "Dispatch", "Dispatch - restricted" now "Service", "Service - restricted"
 	this also ties in more tightly with the user interface menu options making it clearer where it applies
 
-- Work order Cost field restrictions 
-	Only staff user types can even *potentially* see costs of anything on work order.
-	Non staff user types can not see costs at all no matter what role is set for them: customer headoffice or subcontractor types.
-	Cost restrictions are not only hidden in work order user interface but are also sent as zeros in the data from the server so viewing the network traffic will still not reveal the costs to a cost restricted user.
-	Cost restrictions also apply to reporting so a report with cost fields on it will show those values as zero if the current user is restricted from seeing costs 
+* Sub contractors / Technician - Restricted users and Work Orders
+    If a User is set to User type of Sub contractor or if they are a Service type user and are assigned the "Technician - Restricted" role then special limitations apply to them when using the work order form:
 
-	Specifically on work order, costs potentially not shown are for following objects: WorkorderItemParts, WorkOrderItemLabor, WorkOrderItemTravel, WorkOrderItemLoan
-	
-	WorkOrderItemParts costs: in addition to above restrictions, user must have one of the following roles: InventoryRestricted, Inventory, BizAdmin (full), Accounting
-	This means all Technician (and any other) role users will not see costs for these parts by default unless they also have one of those specific roles 
+    * Work order *Item* restrictions    
+        * Theser Users will only be able to access the Work order Items for which they are Scheduled in the work order editing form.  In other words if you do not want a Sub contractor or tech - restricted user to see parts of a work order do not add them to the Scheduled users collection on those work order items
 
-	WorkOrderItemLabor / WorkOrderItemTravel / WorkOrderItemLoan costs: in addition to staff user restrictions, user must have one of the following roles: ServiceRestricted, Service, BizAdmin (full), Accounting
-	This means all Technician (and any other) role users will not see costs for these rates by default unless they also have one of those specific roles 
 
-	New reporting fields
-	Three new boolean fields are now set on work order header data to indicate which costs are hidden:
-	HasPartCosts, HasTravelAndLaborRateCosts, HasLoanItemCosts
+* Work order Cost field restrictions 
+    *Work orders can show Costs for various items on them but these costs are only displayed for a select few users:
+        * Non staff user types (customer headoffice or subcontractor) can not see costs at all no matter what roles are set for them        
+        * WorkOrderItemParts costs: to see these costs, the user must have one of the following roles: InventoryRestricted, Inventory, BizAdmin (full), Accounting      
+        * WorkOrderItemLabor / WorkOrderItemTravel / WorkOrderItemLoan costs: user must have one of the following roles: ServiceRestricted, Service, BizAdmin (full), Accounting
+        * Reporting convenience fields: fields are included on work order header report data to indicate which costs are hidden: HasPartCosts, HasTravelAndLaborRateCosts, HasLoanItemCosts
+        * Costs to restricted users are not only hidden in work order user interface but are also sent as zeros in the data from the server
+        * Cost restrictions also apply to reporting so a report with cost fields on it will show those values as zero if the current user is restricted from seeing costs    
+      
+