diff --git a/home/src/main/resources/config/example.runtime.properties b/home/src/main/resources/config/example.runtime.properties
index 3a5c862e..f665b0fc 100644
--- a/home/src/main/resources/config/example.runtime.properties
+++ b/home/src/main/resources/config/example.runtime.properties
@@ -7,6 +7,11 @@
 # Save a copy of this file as runtime.properties in your VIVO home directory, 
 # and edit the properties as needed for your installation.
 #
+# For more information on specific properties, see the configuration reference
+# or installation options section of the technical documentation for the
+# version of VIVO you are running:
+# https://wiki.duraspace.org/display/VIVO/VIVO+Technical+Documentation 
+#
 # -----------------------------------------------------------------------------
 
 
@@ -295,8 +300,6 @@ VitroConnection.DataSource.validationQuery = SELECT 1
   #  
   # When the following flag is set to enabled, the VIVO home page displays a 
   # global map highlighting the geographical focus of foaf:person individuals. 
-  # For information on the maps, refer to this wiki page:
-  # https://wiki.duraspace.org/x/c4XVAw
   #
 #homePage.geoFocusMaps=enabled
 
@@ -306,9 +309,6 @@ VitroConnection.DataSource.validationQuery = SELECT 1
   # and a "quick" page view that emphasizes the individual's webpage presence. 
   # Implementing this feature requires an installation to develop a web service
   # that captures images of web pages or to use an existing service outside of VIVO. 
-  # 
-  # For more information on implementing multiple profile pages, refer to this 
-  # wiki page: https://wiki.duraspace.org/x/doXVAw
   #
 #multiViews.profilePageTypes=enabled
 
@@ -317,9 +317,6 @@ VitroConnection.DataSource.validationQuery = SELECT 1
   # Tell VIVO to generate HTTP headers on its responses to facilitate caching the 
   # profile pages that it creates. 
   #
-  # For more information, see this wiki page: 
-  # https://wiki.duraspace.org/x/5sQQAg
-  #
   # Developers will likely want to leave caching disabled, since a change to a
   # Freemarker template or to a Java class would not cause the page to be 
   # considered stale.