readme formatting

1 files changed, 1 insertions, 1 deletions

diff --git a/README.md b/README.md
index ee7e9ec..f351dc1 100644
--- a/README.md
+++ b/README.md
@@ -345,7 +345,7 @@ Consultation with the local community on talk-au at https://lists.openstreetmap.
 
 - Existing interpolation way addresses to be replaced with individually mapped address nodes.
 - Imported addresses as lone address nodes, not merged onto existing buildings or other objects.
-- ~~Using `addr:suburb` as a catch-all for the placename/suburb/locality of the address, irrespective of if the value is actually referring to an OSM `place=suburb` or `place=town` or `place=hamlet` etc. (see page 25, section 15 of https://auspost.com.au/content/dam/auspost_corp/media/documents/australia-post-addressing-standards-1999.pdf). ~~ _This was subsequently nullified after deciding to omit `addr:suburb`._
+- ~~Using `addr:suburb` as a catch-all for the placename/suburb/locality of the address, irrespective of if the value is actually referring to an OSM `place=suburb` or `place=town` or `place=hamlet` etc. (see page 25, section 15 of https://auspost.com.au/content/dam/auspost_corp/media/documents/australia-post-addressing-standards-1999.pdf).~~ _This was subsequently nullified after deciding to omit `addr:suburb`._
 - ~~Further to the previous point, where an existing address uses `addr:city` but our conflation indicates that the `addr:city` value should be `addr:suburb` then this will be updated on the existing object.~~ _This was subsequently nullified after deciding to omit `addr:suburb`._
 - Including full address attributes (`addr:suburb`, `addr:state`, `addr:postcode`), even when they could be derived from existing boundaries is contentious with advocates for both options. Due to this, these attributes are omitted.