docs/8.0/ayanova/docs/ay-customize.md

@@ -59,7 +59,11 @@ Some fields by their nature can't be set to required and will not display a Requ
 
 ### Custom fields
 
-Up to 16 custom fields can be enabled on most AyaNova business objects to track information that is specific to your business and not provided in the default AyaNova fields for each object. Custom field data is stored with the business object's record in the database.
+Up to 16 custom fields can be enabled on most AyaNova business objects to track information that is specific to your business and not provided in the default AyaNova fields for each object. 
+
+Custom field data is stored with the business object's record in the database and where possible (text) is indexed for searching.
+
+Custom fields can also be [printed on reports](ay-report-edit.md#custom-fields-in-report-data).
 
 There are three steps to enabling a Custom field:
 
@@ -75,12 +79,16 @@ There are three steps to enabling a Custom field:
     - `Decimal` decimal number input control, fractional
     - `Money` currency control with currency symbol
 
-3.  Change the User's translation(s) to show the desired title above the control: Make a note of the translation key for the custom field. It will be shown just beneath the current translation for that field, for example "Custom5" in the Customer form has an internal translation key of "CustomerCustom5". Save your changes here and then use the translation key to [find and edit the translation](adm-translations.md) so that the desired title shows with the Custom field. There is a `Translation` menu item on the Customize form to save a click.
+3.  Change the User's translation(s) to show the desired title above the control: Make a note of the translation key for the custom field. It will be shown just beneath the current translation for that field, for example "Custom5" in the Customer form has an internal translation key of "CustomerCustom5". Save your changes here and then use the translation key to [find and edit the translation](adm-translations.md) so that the desired title shows with the Custom field. There is a *Translation* menu item on the Customize form to save a click.
 
 ### Changing the title of fields
 
-To change the text displayed to the User above a field, edit any [translations](adm-translations.md) in use for that field's translation key. The internal Translation Key for each field is displayed in the Customize form beneath the current translation of that field's title to simplify finding which translation item needs to be changed. For example on the Customer's Customize form the "Account number" field shows that the translation key is "AccountNumber".
+To change the label text displayed to the User above a field, edit any [translations](adm-translations.md) in use for that field's translation key. The internal Translation Key for each field is displayed in the Customize form beneath the current translation of that field's title to simplify finding which translation item needs to be changed. 
 
-Many translations are re-used when the field contains the same type of data, so, for example an Address field will be used in many forms where and Address is required, not just the Customer form. Keep this in mind when editing translations.
+For example on the Customer's Customize form the "Account number" field shows that the translation key is "AccountNumber".
 
-Radically changing a fields name to something completely different may be a sign that a Custom field should be used instead as in many cases AyaNova expects a certain kind of data to be in a field. For example a phone number field presents a dialer icon beside it to allow a user with a device that can make a phone call to simply click on the dialer icon to call that number. If you change that field to something that isn't a phone number it will break existing functionality.
+Many translations are re-used when the field contains the same type of data, so, for example an Address field will be used in any forms where an Address is required, not just the Customer form. Keep this in mind when editing translations.
+
+Radically changing a field's title to something completely different may be a sign that a [Custom field](#custom-fields) should be used instead as in some cases AyaNova expects a certain kind of data to be in a field. 
+
+For example a phone number field presents a dialer icon beside it to allow a user with a device that can make a phone call to simply click on the dialer icon to call that number. If you change that field to something that isn't a phone number it willn be confusing to the user and break existing functionality.

docs/8.0/ayanova/docs/ay-report-edit.md

@@ -197,7 +197,7 @@ The report data provided comes directly from the Server and is not translated or
 
 #### Custom fields in report data
 
-In AyaNova an object can have up to 16 customizable fields of extra data. In the `SAMPLE DATA` area of the reported editor interface you can see the custom field data, for example:
+In AyaNova an object can have up to 16 customizable fields of extra data. In the *SAMPLE DATA* area of the report editor interface you can see the custom field data, for example:
 
 ```json
 "CustomFields": {

docs/8.0/ayanova/docs/ay-start-form-wiki.md

@@ -10,7 +10,7 @@ Wikis support URL hyperlinks, can embed images, offer rich formatting options an
 
 Wiki's are formatted using **[Markdown](https://en.wikipedia.org/wiki/Markdown)** a plain text formatting language.
 
-This AyaNova manual itself is written in Markdown.
+AyaNova manual pages are written in Markdown.
 
 Below is a quick reference guide to AyaNova Markdown showing the source document with most features available and how it will render.