diff --git a/application/templates/pages/about/about.md b/application/templates/pages/about/about.md
index 149e038e..f2def6ae 100644
--- a/application/templates/pages/about/about.md
+++ b/application/templates/pages/about/about.md
@@ -13,6 +13,8 @@ Our platform collects planning and housing data from local planning authorities
This product is still in development
+Because we are working on this product:
+
- the data does not yet cover all of England
- the data we have collected is not yet complete (there may be things you expect to see that are currently missing)
- legislation designed to mandate these standards is still [in Parliament](https://bills.parliament.uk/bills/3155)
diff --git a/application/templates/pages/guidance/specifications/article-4-direction.md b/application/templates/pages/guidance/specifications/article-4-direction.md
index 95bde4bb..3557e263 100644
--- a/application/templates/pages/guidance/specifications/article-4-direction.md
+++ b/application/templates/pages/guidance/specifications/article-4-direction.md
@@ -32,6 +32,7 @@ A reference or ID for each article 4 direction that is:
- permanent - it doesn’t change when the dataset is updated
If you don’t use a reference already, you will need to create one. This can be a short set of letters or numbers.
+
Example: `A4D1`
### name
@@ -73,12 +74,14 @@ Example: `1984-03-28`
### end-date
If applicable, the date that the article 4 direction was no longer in effect, written in `YYYY-MM-DD` format. If this does not apply, leave the cell blank.
+
Example: `1999-01-20`
### entry-date
The date this dataset was created or last updated, written in `YYYY-MM-DD` format.
-Example: 2022-12-20
+
+Example: `2022-12-20`
---
@@ -159,6 +162,7 @@ Example: `1984-03-28`
### end-date
If applicable, the date that the article 4 direction was no longer in effect, written in `YYYY-MM-DD` format. If this does not apply, leave the cell blank.
+
Example: `1999-01-20`
### entry-date
diff --git a/application/templates/pages/guidance/specifications/conservation-area.md b/application/templates/pages/guidance/specifications/conservation-area.md
index 877f1415..445abe1d 100644
--- a/application/templates/pages/guidance/specifications/conservation-area.md
+++ b/application/templates/pages/guidance/specifications/conservation-area.md
@@ -93,6 +93,7 @@ These documents are the authoritative source and provide the context around the
- gazette entries
The dataset must contain at least one entry (row) for each conservation area document.
+
It must containing the following fields (columns):
### reference
@@ -102,14 +103,17 @@ A reference or ID for each document that is:
- permanent - it doesn't change when the dataset is updated
If you don't use a reference already, you will need to create one. This can be a short set of letters or numbers.
+
Example: `CADOC01`
### name
The title of the document.
+
Example: `Notice of Old Market conservation area designation`
### conservation-area
The reference for the conservation area this document refers to, as used in the conservation area dataset.
+
Example: `CA1`
### documentation-url
@@ -121,6 +125,7 @@ Example: `http://www.LPAwebsite.org.uk/data#conservationarea1`
### document-url
The URL of the document.
+
Example: `http://www.LPAwebsite.org.uk/conservationarea1.pdf`
### document-type
@@ -135,14 +140,17 @@ Optional text on how this data was made or produced, or how it can be interprete
### start-date
The date the document was published, written in `YYYY-MM-DD` format.
+
Example: `1984-03-28`
### end-date
The date the document was withdrawn or superseded by another document, written in `YYYY-MM-DD` format. Leave this blank if the document is still relevant to planning.
+
Example: `1984-03-28`
### entry-date
The date this entry was created or updated, written in `YYYY-MM-DD` format.
+
Example: `1984-03-28`
---
diff --git a/application/templates/pages/guidance/specifications/tree-preservation-order.md b/application/templates/pages/guidance/specifications/tree-preservation-order.md
index ec7a4a05..459f1145 100644
--- a/application/templates/pages/guidance/specifications/tree-preservation-order.md
+++ b/application/templates/pages/guidance/specifications/tree-preservation-order.md
@@ -70,7 +70,7 @@ The date a tree preservation order was made available to the public. The tree or
Write in YYYY-MM-DD format.
-Example: '2022-12-20'
+Example: `2022-12-20`
### start-date
@@ -84,7 +84,7 @@ The date a tree preservation order is confirmed as being in effect, and the tree
Write in YYYY-MM-DD format.
-Example: '2022-12-20'
+Example: `2022-12-20`
### end-date