Revised help text. [ref #813]

src/main/java/Bundle.properties

@@ -234,20 +234,20 @@ dashboard.card.harvestingserver.disabled=OAI server disabled
 
 dashboard.card.harvestingserver.btn.manage=Manage Server
 dashboard.card.metadataexport.header=Metadata Export
-dashboard.card.metadataexport.message=You can schedule export through the API only. Check out our {0}API Guide{1} for more information on using the Dataverse APIs.
+dashboard.card.metadataexport.message=Dataset metadata export is only available through the {0} API. Learn how to do this in the {0} {1}API Guide{2}.
 
 #harvestclients.xhtml
 harvestclients.title=Manage Harvesting Clients
 harvestclients.toptip= - Harvesting can be scheduled to run on a regular basis, or on demand, here or via the REST API.
 
-harvestclients.noClients.label=No clients are presently configured.
-harvestclients.noClients.why.header=Why Use Harvesting?
-harvestclients.noClients.why.reason1="Harvesting" is a process of exchanging metadata with other repositories. As a harvesting <b><i>client</i></b>, your Dataverse gathers metadata records from remote sources. These can be other Dataverse instances, or other archives that support OAI-PMH, the standard harvesting protocol. 
-harvestclients.noClients.why.reason2=Collected metadata records are made searchable by local users. Clicking on a harvested dataset in the search results takes the user to its original remote location. Once harvested, datasets cannot be edited. 
+harvestclients.noClients.label=No clients are configured.
+harvestclients.noClients.why.header=What is Harvesting?
+harvestclients.noClients.why.reason1=Harvesting is a process of exchanging metadata with other repositories. As a harvesting <b><i>client</i></b>, your Dataverse gathers metadata records from remote sources. These can be other Dataverse instances, or other archives that support OAI-PMH, the standard harvesting protocol. 
+harvestclients.noClients.why.reason2=Collected metadata records are made searchable by users. Clicking on a harvested dataset in the search results takes the user to the original repository. Harvested datasets cannot be edited in your Dataverse installation. 
 harvestclients.noClients.how.header=How To Use Harvesting
-harvestclients.noClients.how.tip1=To harvest metadata, a <i>Harvesting Client</i> is created and configured for each remote repository. Note that when creating a client you will need to select an already existing local dataverse to host datasets harvested.
+harvestclients.noClients.how.tip1=To harvest metadata, a <i>Harvesting Client</i> is created and configured for each remote repository. Note that when creating a client you will need to select an existing local dataverse to host harvested datasets.
 
-harvestclients.noClients.how.tip2=Harvested records can be kept in sync through scheduled incremental updates, daily or weekly. Alternatively, harvests can be run on demand, from this page or via the REST API.
+harvestclients.noClients.how.tip2=Harvested records can be kept in sync with the original repository through scheduled incremental updates, daily or weekly. Alternatively, harvests can be run on demand, from this page or via the REST API.
 harvestclients.noClients.getStarted=To get started, click on the Add Client button above. To learn more about Harvesting, visit the <a href="{0}/{1}/user/index.html#index" title="Harvesting - Dataverse User Guide" target="_blank">Harvesting</a> section of the User Guide.
 
 harvestclients.tab.header.name=Nickname
@@ -263,7 +263,7 @@ harvestclients.tab.header.action.btn.delete.dialog.tip=Are you sure you want to
 harvestclients.actions.runharvest.success=Successfully started an asynchronous harvest for client "{0}" (please reload the page to check on the harvest results).
 
 harvestclients.newClientDialog.title.new=Create Harvesting Client
-harvestclients.newClientDialog.help=Configure a new client to harvest content from a remote server. You will be able schedule harvesting to take place on a regular basis, or leave it unscheduled and run it on demand only.
+harvestclients.newClientDialog.help=Configure a new client to harvest content from a remote server. You will be able to schedule harvesting to take place on a regular basis, or leave it unscheduled and run it on demand only.
 harvestclients.newClientDialog.nickname=Nickname
 harvestclients.newClientDialog.nickname.helptext=Consists of letters, digits, underscores (_) and dashes (-).
 harvestclients.newClientDialog.nickname.required=Client nickname cannot be empty!
@@ -287,7 +287,7 @@ harvestclients.newClientDialog.dataverse=Local Dataverse
 harvestclients.newClientDialog.dataverse.menu.enterName=Enter Dataverse Alias
 harvestclients.newClientDialog.dataverse.menu.header=Dataverse Name (Affiliate), Alias
 harvestclients.newClientDialog.dataverse.menu.invalidMsg=No matches found
-harvestclients.newClientDialog.dataverse.helptext=Local dataverse that will host the datasets harvested from this remote resource.
+harvestclients.newClientDialog.dataverse.helptext=Dataverse that will host the datasets harvested from this remote resource.
 harvestclients.newClientDialog.dataverse.required=You must select an existing dataverse for this harvesting client
 
 harvestclients.newClientDialog.oaiSets=OAI Set
@@ -332,12 +332,12 @@ harvestserver.toptip= - Define sets of local datasets that will be available for
 harvestserver.service.label=OAI Server
 harvestserver.service.enabled=Enabled
 harvestserver.service.disabled=Disabled
-harvestserver.service.empty=No sets are presently configured.
+harvestserver.service.empty=No sets are configured.
 harvestserver.service.enable.success=OAI Service has been successfully enabled.
 
 harvestserver.noSets.why.header=What is a Harvesting Server?
-harvestserver.noSets.why.reason1="Harvesting" is a process of exchanging metadata with other repositories. As a harvesting <b><i>server</i></b>, your Dataverse can make some of the local dataset metadata available to remote harvesting clients. These can be other Dataverse instances, or any other clients that support OAI-PMH harvesting protocol. 
-harvestserver.noSets.why.reason2=Only the published, non-restricted datasets in your Dataverse will be harvestable. Remote clients will normally keep their records in sync through scheduled incremental updates, daily or weekly. Thus minimizing the load on your server. Note that it is only the metadata that are harvested. Remote harvesters will generally not attempt to download the available data files. 
+harvestserver.noSets.why.reason1=Harvesting is a process of exchanging metadata with other repositories. As a harvesting <b><i>server</i></b>, your Dataverse can make some of the local dataset metadata available to remote harvesting clients. These can be other Dataverse instances, or any other clients that support OAI-PMH harvesting protocol. 
+harvestserver.noSets.why.reason2=Only the published, unrestricted datasets in your Dataverse are able to be harvested. Remote clients normally keep their records in sync through scheduled incremental updates, daily or weekly, thus minimizing the load on your server. Note that it is only the metadata that are harvested. Remote harvesters will generally not attempt to download the available data files. 
 
 harvestserver.noSets.how.header=How to run a Harvesting Server?
 harvestserver.noSets.how.tip1=Harvesting server can be enabled or disabled on this page. 

src/main/webapp/dashboard.xhtml

@@ -81,6 +81,7 @@
                                             <p class="help-block">
                                                 <span class="glyphicon glyphicon-info-sign"/>
                                                 <h:outputFormat value=" #{bundle['dashboard.card.metadataexport.message']}" escape="false">
+                                                    <f:param value="#{dataverseServiceBean.findRootDataverse().displayName}"/>
                                                     <f:param value="&lt;a href=&#34;#{systemConfig.guidesBaseUrl}/#{systemConfig.version}/api&#34; target=&#34;_blank&#34;&gt;"/>
                                                     <f:param value="&lt;/a&gt;"/>
                                                 </h:outputFormat>