diff --git a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md
index 7e182947..bab8a58c 100644
--- a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md
+++ b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md
@@ -3,8 +3,6 @@
 Starting with version 8, AyaNova was completely re-written.
 Our goals in this were to make AyaNova easier to use, modernize aging code, take advantage of the latest technologies and move to a modern run on any device approach.
 
-This page documents the changes most relevant to everyday users of AyaNova however there were also many other technical changes of interest to system administrators and installers which are documented in our [Technical changes from v7](ops-technical-changes-from-v7.md) page of this documentation.
-
 ## User interface changes from v7
 
 AyaNova 7 had several different user interfaces: the main interface was a Windows desktop application and as optional add-on products we had several different web browser interfaces for varying levels of devices. Each web interface had a limited sub-set of the full features in the Windows application and required separate installation and configuration procedures.
diff --git a/docs/8.0/ayanova/docs/ops-config-backup-pgdump-path.md b/docs/8.0/ayanova/docs/ops-config-backup-pgdump-path.md
index 77734522..f23719a3 100644
--- a/docs/8.0/ayanova/docs/ops-config-backup-pgdump-path.md
+++ b/docs/8.0/ayanova/docs/ops-config-backup-pgdump-path.md
@@ -1,4 +1,4 @@
-# BACKUP UTILITY "pg_dump" PATH SETTING
+# Backup utility "pg_dump" path setting
 
 This setting controls where AyaNova will find the PostgreSQL pg_dump utility used forautomated backups.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-data-path.md b/docs/8.0/ayanova/docs/ops-config-data-path.md
index 801005cc..0d326163 100644
--- a/docs/8.0/ayanova/docs/ops-config-data-path.md
+++ b/docs/8.0/ayanova/docs/ops-config-data-path.md
@@ -1,4 +1,4 @@
-# DATA PATH SETTING
+# Data path setting
 
 This setting controls where AyaNova stores it's data by default and is required to be present unless all other path related configuration settings are specified individually.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-db.md b/docs/8.0/ayanova/docs/ops-config-db.md
index 0e239932..64d2d0c9 100644
--- a/docs/8.0/ayanova/docs/ops-config-db.md
+++ b/docs/8.0/ayanova/docs/ops-config-db.md
@@ -1,4 +1,4 @@
-# DATABASE
+# Database
 
 AyaNova uses [PostgreSQL](https://www.postgresql.org/) as it's database server in all configurations, no other database is supported.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-default-translation.md b/docs/8.0/ayanova/docs/ops-config-default-translation.md
index 50d969d1..c9f6164c 100644
--- a/docs/8.0/ayanova/docs/ops-config-default-translation.md
+++ b/docs/8.0/ayanova/docs/ops-config-default-translation.md
@@ -1,4 +1,4 @@
-# DEFAULT TRANSLATION SETTING
+# Default translation setting
 
 This setting controls the default language for text displayed to users in the AyaNova user interface.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-environment-variables.md b/docs/8.0/ayanova/docs/ops-config-environment-variables.md
index 15238c3a..f9fe158f 100644
--- a/docs/8.0/ayanova/docs/ops-config-environment-variables.md
+++ b/docs/8.0/ayanova/docs/ops-config-environment-variables.md
@@ -1,4 +1,4 @@
-# AYANOVA CONFIGURATION GUIDE
+# AyaNova configuration guide
 
 Most of the AyaNova configuration is stored inside the database and set from within the AyaNova web application, however anything related to starting the server can not be stored in the database so external configuration is required for some settings.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-folder-backup-files.md b/docs/8.0/ayanova/docs/ops-config-folder-backup-files.md
index 14d6d7c6..f9bfecd9 100644
--- a/docs/8.0/ayanova/docs/ops-config-folder-backup-files.md
+++ b/docs/8.0/ayanova/docs/ops-config-folder-backup-files.md
@@ -1,4 +1,4 @@
-# BACKUP FILES FOLDER SETTING
+# Backup files folder setting
 
 This setting controls where AyaNova stores backup and restore files used by the backup and restore features built into AyaNova.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-folder-temporary-files.md b/docs/8.0/ayanova/docs/ops-config-folder-temporary-files.md
index 430c652c..bf25394b 100644
--- a/docs/8.0/ayanova/docs/ops-config-folder-temporary-files.md
+++ b/docs/8.0/ayanova/docs/ops-config-folder-temporary-files.md
@@ -1,4 +1,4 @@
-# TEMPORARY SERVER FILES FOLDER SETTING
+# Temporary server files folder setting
 
 This setting controls where AyaNova stores files temporarily while servicing requests such as report generation etc.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-folder-user-files.md b/docs/8.0/ayanova/docs/ops-config-folder-user-files.md
index f7e4a3b4..d9c3c76a 100644
--- a/docs/8.0/ayanova/docs/ops-config-folder-user-files.md
+++ b/docs/8.0/ayanova/docs/ops-config-folder-user-files.md
@@ -1,4 +1,4 @@
-# ATTACHMENTS FOLDER SETTING
+# Attachments folder setting
 
 This setting controls where AyaNova stores user uploaded files used by features that allow file attachment or uploads.
 AyaNova stores these files with special names calculated from their digital signature (checksum) in a subdirectory in the folder specified.
diff --git a/docs/8.0/ayanova/docs/ops-config-report-render-browser-path.md b/docs/8.0/ayanova/docs/ops-config-report-render-browser-path.md
index 40dc7f0b..e6efb530 100644
--- a/docs/8.0/ayanova/docs/ops-config-report-render-browser-path.md
+++ b/docs/8.0/ayanova/docs/ops-config-report-render-browser-path.md
@@ -1,4 +1,4 @@
-# REPORT RENDER BROWSER PATH SETTING
+# Report render browser path setting
 
 This optional setting sets the _full_ path to the Chromium web browser executable that is used by AyaNova to render reports.
 
diff --git a/docs/8.0/ayanova/docs/ops-config-set-superuser-pw.md b/docs/8.0/ayanova/docs/ops-config-set-superuser-pw.md
index d3db7bb7..39bae217 100644
--- a/docs/8.0/ayanova/docs/ops-config-set-superuser-pw.md
+++ b/docs/8.0/ayanova/docs/ops-config-set-superuser-pw.md
@@ -1,4 +1,4 @@
-# SUPER USER PASSWORD OVERRIDE
+# SuperUser password override
 
 In the event that the SuperUser password is lost it can be reset using this setting.
 Upon booting up the server will reset the current SuperUser User account password to this value.
diff --git a/docs/8.0/ayanova/docs/ops-config-use-urls.md b/docs/8.0/ayanova/docs/ops-config-use-urls.md
index 02eea411..57fc8271 100644
--- a/docs/8.0/ayanova/docs/ops-config-use-urls.md
+++ b/docs/8.0/ayanova/docs/ops-config-use-urls.md
@@ -1,4 +1,4 @@
-# PORT / URL SETTING
+# Port / URL setting
 
 You can control the port and URL that the AyaNova server will listen on via environment variable or command line parameter.
 
diff --git a/docs/8.0/ayanova/docs/ops-error-codes.md b/docs/8.0/ayanova/docs/ops-error-codes.md
index 8cce0cc2..21156121 100644
--- a/docs/8.0/ayanova/docs/ops-error-codes.md
+++ b/docs/8.0/ayanova/docs/ops-error-codes.md
@@ -1,4 +1,4 @@
-# SERVER ERROR CODES
+# Server error codes
 #b4beta (clean up, remove unused error codes check if any others missing)
 AyaNova will provide a server error code when an error arises.
 All AyaNova server error codes start with the letter E followed by a number in the range 1000-1999.
diff --git a/docs/8.0/ayanova/docs/ops-form-backup.md b/docs/8.0/ayanova/docs/ops-form-backup.md
index 0f85e8fe..f1db5324 100644
--- a/docs/8.0/ayanova/docs/ops-form-backup.md
+++ b/docs/8.0/ayanova/docs/ops-form-backup.md
@@ -1,4 +1,4 @@
-# OPERATIONS BACKUP FORM
+# Operations backup form
 
 AyaNova can automatically back up to the local file system once per day at a selected time.
 
diff --git a/docs/8.0/ayanova/docs/ops-import-v7.md b/docs/8.0/ayanova/docs/ops-import-v7.md
index 8d3e5203..3c59b02c 100644
--- a/docs/8.0/ayanova/docs/ops-import-v7.md
+++ b/docs/8.0/ayanova/docs/ops-import-v7.md
@@ -1,4 +1,4 @@
-## OVERVIEW
+# Migrating from AyaNova 7
 
 This is the technical guide to the migration to v8 process.  
 
diff --git a/docs/8.0/ayanova/docs/ops-install-linux-desktop.md b/docs/8.0/ayanova/docs/ops-install-linux-desktop.md
index d1227666..56be4b45 100644
--- a/docs/8.0/ayanova/docs/ops-install-linux-desktop.md
+++ b/docs/8.0/ayanova/docs/ops-install-linux-desktop.md
@@ -1,4 +1,4 @@
-# AYANOVA INSTALLATION - LINUX DESKTOP
+# AyaNova installation - linux desktop
 
 Please read through all the instructions below **before** proceeding with installation to be sure everything is available and ready.
 
diff --git a/docs/8.0/ayanova/docs/ops-install-linux-server.md b/docs/8.0/ayanova/docs/ops-install-linux-server.md
index ba06b774..a6f19fba 100644
--- a/docs/8.0/ayanova/docs/ops-install-linux-server.md
+++ b/docs/8.0/ayanova/docs/ops-install-linux-server.md
@@ -1,4 +1,4 @@
-# AYANOVA INSTALLATION - LINUX SERVER
+# AyaNova installation - linux server
 
 Please read through all the instructions below **before** proceeding with installation to be sure everything is available and ready.
 
diff --git a/docs/8.0/ayanova/docs/ops-install-linux.md b/docs/8.0/ayanova/docs/ops-install-linux.md
index 7d234874..0fbaf3cf 100644
--- a/docs/8.0/ayanova/docs/ops-install-linux.md
+++ b/docs/8.0/ayanova/docs/ops-install-linux.md
@@ -1,4 +1,4 @@
-# AYANOVA LINUX INSTALLATION
+# AyaNova linux installation
 
 Choose how AyaNova will be used for specific Linux installation instructions. Note that it's possible to switch to an alternative configuration via backup and restore if needs change later however if there is a possibility that AyaNova will be accessed from the internet it's recommended to install using the NGINX proxy server instructions below.
 
@@ -13,4 +13,3 @@ This type of install is appropriate for using AyaNova locally on a single person
 When more than one user will be accessing AyaNova it can be set up on a Linux server either on-premise or with a Linux hosting provider, for example [Digitalocean](https://www.digitalocean.com/) or [Linode](https://www.linode.com/) that provides full shell access to a virtual or physical server.
 
 [Server install guide](ops-install-linux-server.md)
-
diff --git a/docs/8.0/ayanova/docs/ops-install-windows-iis.md b/docs/8.0/ayanova/docs/ops-install-windows-iis.md
index fdcdb5e9..bb79547a 100644
--- a/docs/8.0/ayanova/docs/ops-install-windows-iis.md
+++ b/docs/8.0/ayanova/docs/ops-install-windows-iis.md
@@ -1,4 +1,4 @@
-# AYANOVA INSTALLATION - WINDOWS IIS HOSTED
+# AyaNova installation - Windows IIS hosted
 
 Please read through all the instructions below **before** proceeding with installation to be sure everything is available and ready.
 
diff --git a/docs/8.0/ayanova/docs/ops-install-windows-lan.md b/docs/8.0/ayanova/docs/ops-install-windows-lan.md
index f2adcbd2..b6980c93 100644
--- a/docs/8.0/ayanova/docs/ops-install-windows-lan.md
+++ b/docs/8.0/ayanova/docs/ops-install-windows-lan.md
@@ -1,4 +1,4 @@
-# AYANOVA INSTALLATION - WINDOWS LOCAL NETWORK
+# AyaNova installation - Windows local network
 
 Please read through all the instructions below **before** proceeding with installation to be sure everything is available and ready.
 
diff --git a/docs/8.0/ayanova/docs/ops-install-windows-single.md b/docs/8.0/ayanova/docs/ops-install-windows-single.md
index 1245c052..e7d84678 100644
--- a/docs/8.0/ayanova/docs/ops-install-windows-single.md
+++ b/docs/8.0/ayanova/docs/ops-install-windows-single.md
@@ -1,4 +1,4 @@
-# AYANOVA INSTALLATION - WINDOWS SINGLE
+# AyaNova installation - Windows single
 
 Please read through all the instructions below **before** proceeding with installation to be sure everything is available and ready.
 
diff --git a/docs/8.0/ayanova/docs/ops-install-windows.md b/docs/8.0/ayanova/docs/ops-install-windows.md
index 879a5594..2b2ec7ac 100644
--- a/docs/8.0/ayanova/docs/ops-install-windows.md
+++ b/docs/8.0/ayanova/docs/ops-install-windows.md
@@ -1,4 +1,4 @@
-# AYANOVA WINDOWS INSTALLATION
+# AyaNova Windows installation
 
 Choose how AyaNova will be used for specific Windows installation instructions. Note that it's possible to switch to an alternative configuration via backup and restore if needs change later however if there is a possibility that AyaNova will be accessed from the internet it's recommended to install as an IIS hosted application.
 
diff --git a/docs/8.0/ayanova/docs/ops-install.md b/docs/8.0/ayanova/docs/ops-install.md
index 493dae34..8b47d27f 100644
--- a/docs/8.0/ayanova/docs/ops-install.md
+++ b/docs/8.0/ayanova/docs/ops-install.md
@@ -1,6 +1,6 @@
-# AYANOVA SERVER INSTALLATION
+# AyaNova server installation
 
-The AyaNova server will run on Windows or Linux.
+The AyaNova server can be installed on Windows or Linux.
 
 Choose your operating system for specific instructions:
 
diff --git a/docs/8.0/ayanova/docs/ops-intro.md b/docs/8.0/ayanova/docs/ops-intro.md
index 224e61e4..5cf8f4bb 100644
--- a/docs/8.0/ayanova/docs/ops-intro.md
+++ b/docs/8.0/ayanova/docs/ops-intro.md
@@ -1,4 +1,4 @@
-# AYANOVA SERVER OPERATIONS GUIDE
+# AyaNova server operations guide
 
 ## AyaNova system architecture
 
diff --git a/docs/8.0/ayanova/docs/ops-maintenance.md b/docs/8.0/ayanova/docs/ops-maintenance.md
index 6daac4d9..464089e7 100644
--- a/docs/8.0/ayanova/docs/ops-maintenance.md
+++ b/docs/8.0/ayanova/docs/ops-maintenance.md
@@ -1,4 +1,4 @@
-# SERVER MAINTENANCE
+# Server maintenance
 
 An AyaNova server should require very little ongoing maintenance, however there are a few things that need to be monitored on a regular basis.
 
diff --git a/docs/8.0/ayanova/docs/ops-metrics.md b/docs/8.0/ayanova/docs/ops-metrics.md
index e88fd24d..835f6020 100644
--- a/docs/8.0/ayanova/docs/ops-metrics.md
+++ b/docs/8.0/ayanova/docs/ops-metrics.md
@@ -1,4 +1,4 @@
-# METRICS 
+# Metrics 
 
 [under construction]
 
diff --git a/docs/8.0/ayanova/docs/ops-migration-from-7.md b/docs/8.0/ayanova/docs/ops-migration-from-7.md
deleted file mode 100644
index 9da0bacc..00000000
--- a/docs/8.0/ayanova/docs/ops-migration-from-7.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Migrating from AyaNova 7
-
-#b4beta (already have this page in ops-import-v7.md need to figure out which to use what links and remove one)
diff --git a/docs/8.0/ayanova/docs/ops-notification-settings.md b/docs/8.0/ayanova/docs/ops-notification-settings.md
deleted file mode 100644
index 5fe453f7..00000000
--- a/docs/8.0/ayanova/docs/ops-notification-settings.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# NOTIFICATION SETTINGS
-#b4beta (consolidate all notificatin ops stuff into one page, check links)
-## SMTP settings
-This form is used to configure SMTP mail server settings for notification purposes.
-
-## Notify event delivery queue
-From the menu you can access the Notify event delivery queue which lists all the events that are in the queue for delivery and has an option to delete delivery items if they haven't gone out yet.  This is only pending items, delivered (or failed delivery) items are logged separately and removed from the queue automatically.
diff --git a/docs/8.0/ayanova/docs/ops-notification-system.md b/docs/8.0/ayanova/docs/ops-notification-system.md
index 808589d3..c48e45c0 100644
--- a/docs/8.0/ayanova/docs/ops-notification-system.md
+++ b/docs/8.0/ayanova/docs/ops-notification-system.md
@@ -1,5 +1,5 @@
-# NOTIFICATION SYSTEM
-
+# Notification system
+000000000000 todo: see bottom 000000000000000000000
 AyaNova has a built in notification system that alerts users to events of interest that occur in AyaNova.
 
 ## Types of notifications
@@ -18,7 +18,7 @@ There are two methods of delivering notifications:
 
 ## Email delivery configuration
 
-The in application delivery does not require any configuration however the SMTP delivery is required to be set up in the [Ops Notification settings](ops-notification-settings.md) form.
+The in application delivery does not require any configuration however the SMTP delivery is required to be set up in the [Ops Notification settings](ops-notification-system.md) form.
 
 ## Operations specific notification events
 
@@ -29,3 +29,14 @@ Operations users should subscribe to several key notifications related directly
 - ServerOperationsProblem - sent whenever the server encounters any unusual condition or error that could be critical for the continuing operation of the AyaNova server
 
 These are in addition to the normal operations methods of monitoring the health and status of the server such as [server logs](ops-log.md), [metrics](ops-metrics.md), [job queue](ops-jobs.md) etc.
+
+
+00000000000000000
+TODO:  consolidate the ops notification settings page to here:
+# NOTIFICATION SETTINGS
+#b4beta (consolidate all notificatin ops stuff into one page, check links)
+## SMTP settings
+This form is used to configure SMTP mail server settings for notification purposes.
+
+## Notify event delivery queue
+From the menu you can access the Notify event delivery queue which lists all the events that are in the queue for delivery and has an option to delete delivery items if they haven't gone out yet.  This is only pending items, delivered (or failed delivery) items are logged separately and removed from the queue automatically.
diff --git a/docs/8.0/ayanova/docs/ops-restore.md b/docs/8.0/ayanova/docs/ops-restore.md
index 1ff9fe1e..c7cbb65d 100644
--- a/docs/8.0/ayanova/docs/ops-restore.md
+++ b/docs/8.0/ayanova/docs/ops-restore.md
@@ -1,4 +1,4 @@
-# RESTORE AYANOVA BACKUP
+# Restore from backup
 
 Restoring an [AyaNova backup](ops-form-backup.md) is done manually through the operating system.
 
@@ -97,9 +97,8 @@ The restore will complete normally without any message if successful.
 AyaNova can be re-started at this point, for server type installations restart through the IIS 'site' in Windows or the Service in Linux. If using the desktop single Windows installation, stop the PostgreSQL started in the earlier restore step by typing `ctrl-c` in the PostgreSQL console window then start AyaNova from the desktop launcher as normally.
 
 ### Verify the data
+
 - Verify database: login to AyaNova, check that the most recent data that should be in the database backup is present
-- Verify attachments: First examine the list of attachments that AyaNova knows about in the database by opening the Adminstration -> Attached files. This list shows the attachments that AyaNova *expects* not necessarily what is physically present so select an attachment listed to open the record that attachment is connected to and confirm the physical file is actually present by opening the file in the attachments area of the form.  If the file won't open verify that the attachment files are restored to the attachments folder where AyaNova expects to find them and not in another folder or sub folder and check again and also verify it's not just an issue with that one attachment by checking or more other attachment files in the same way.
+- Verify attachments: First examine the list of attachments that AyaNova knows about in the database by opening the Adminstration -> Attached files. This list shows the attachments that AyaNova _expects_ not necessarily what is physically present so select an attachment listed to open the record that attachment is connected to and confirm the physical file is actually present by opening the file in the attachments area of the form. If the file won't open verify that the attachment files are restored to the attachments folder where AyaNova expects to find them and not in another folder or sub folder and check again and also verify it's not just an issue with that one attachment by checking or more other attachment files in the same way.
 
 There is no need to shut down the server if the attachment files need to be moved to the correct folder.
-
-
diff --git a/docs/8.0/ayanova/docs/ops-technical-changes-from-v7.md b/docs/8.0/ayanova/docs/ops-technical-changes-from-v7.md
deleted file mode 100644
index bf42e5b3..00000000
--- a/docs/8.0/ayanova/docs/ops-technical-changes-from-v7.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# OPERATIONS INTRO Placeholder
-#b4beta (what links here, do we need it?)
-- docs link here to explain what the AyaNoav server is so start with a server section and explain client server aspects briefly in overview
-- Then go on to the basic sections of ops starting with installation then config and then ongoing maintenance and metrics etc
\ No newline at end of file
diff --git a/docs/8.0/ayanova/mkdocs.yml b/docs/8.0/ayanova/mkdocs.yml
index f8eebe6a..5e934b4e 100644
--- a/docs/8.0/ayanova/mkdocs.yml
+++ b/docs/8.0/ayanova/mkdocs.yml
@@ -131,7 +131,7 @@ nav:
     - 'Linux desktop': 'ops-install-linux-desktop.md'
     - 'Linux server': 'ops-install-linux-server.md'
   - Migration:
-    - 'Migrating from AyaNova 7': 'ops-migration-from-7.md'
+    - 'Migrating from AyaNova 7': 'ops-import-v7.md'
   - Backup & Restore:
     - 'Backup': 'ops-form-backup.md'
     - 'Restore': 'ops-restore.md'
@@ -142,7 +142,7 @@ nav:
     - 'Server log': 'ops-log.md'
     - 'Server metrics': 'ops-metrics.md'
     - 'Profile': 'ops-profile.md'
-    - 'Notification settings': 'ops-notification-settings.md'  
+    - 'Notification settings': 'ops-notification-system.md'  
     - 'Backup': 'ops-form-backup.md'
   - Technical:
     - 'Maintenance': 'ops-maintenance.md'
@@ -161,8 +161,7 @@ nav:
     - 'Security and JWT web tokens': 'ops-config-jwt-secret.md'  
     - 'SuperUser password reset': 'ops-config-set-superuser-pw.md'        
     - 'Server error codes': 'ops-error-codes.md'
-    - 'Technical changes from v7': 'ops-technical-changes-from-v7.md'
-    - 'Importing from older AyaNova': 'ops-import-v7.md'
+    - 'Migrating from AyaNova 7': 'ops-import-v7.md'
     - 'Metrics': 'ops-metrics.md'
     - 'Notification system': 'ops-notification-system.md'
     - 'Notification queue': 'ops-notify-queue.md'