Locale -> Translation

devdocs/specs/core-main-grids.txt

@@ -7,7 +7,7 @@ Proposed system is a hybrid grid system that has two modes to take into account
         - In this mode only one column shows and it's formatted according to the Display Format Template
         - DisplayFormatTemplate is specd in the core-display-format-template-system.txt doc
         - So the user chooses which columns to show in a small factor themselves, default is name only or equivalent
-        - As the client already does all the presentation and locale formatting it will also handle mini column concatenation
+        - As the client already does all the presentation and translation formatting it will also handle mini column concatenation
         - The server's responsibility for mini is to use the mini format template which may well have different columns defined than the full
           - Return the data just the same as for the wide template but it's very likely different data
 
@@ -62,7 +62,7 @@ Server
                 - Optional: ID value (if the object is openable **** MUST CHECK RIGHTS ALSO HERE **** then this is the id to open for the client to put a hyperlink on that column)
                 - To save bandwidth abbreviations are used in the column definitions:
                   - ColumnsJSON=@"""columns"":[ {""cm"":""Widget"",""dt"":""text"",""ay"":"+ AyaType.Widget.ToString()+ "}]";
-                  - cm=column name locale key, dt=AyDataType, ay=AyaType to open on click of that column field (optional, not present if not openable)
+                  - cm=column name translation key, dt=AyDataType, ay=AyaType to open on click of that column field (optional, not present if not openable)
                 - rid flagged column in each row is *ALWAYS* the rowID column specified in objectfields with it's sql attributes
     - For example (wide list):
         data:{