tweaks #10343

Author: pdurbin

doc/release-notes/6.4-release-notes.md

@@ -213,27 +213,25 @@ When any `ApiBlockingFilter` policy applies to a request, the JSON in the body o
 
 See also #10508, #10672 and #10722.
 
-### Cleanup of Temp Directories 
+### Cleanup of Temp Directories
 
-In this release we addressed an issue where copies of files uploaded via the UI were left in one specific temp directory (`.../domain1/uploads` by default). We would like to remind all the installation admins that it is strongly recommended to have some automated (and aggressive) cleanup mechanisms in place for all the temp directories used by Dataverse. For example, at Harvard/IQSS we have the following configuration for the PrimeFaces uploads directory above: (note that, even with this fix in place, PrimeFaces will be leaving a large number of small log files in that location) 
+In this release we addressed an issue where copies of files uploaded via the UI were left in one specific temp directory (`.../domain1/uploads` by default). We would like to remind all the installation admins that it is strongly recommended to have some automated (and aggressive) cleanup mechanisms in place for all the temp directories used by Dataverse. For example, at Harvard/IQSS we have the following configuration for the PrimeFaces uploads directory above: (note that, even with this fix in place, PrimeFaces will be leaving a large number of small log files in that location)
 
-Instead of the default location (`.../domain1/uploads`) we use a directory on a dedicated partition, outside of the filesystem where Dataverse is installed, via the following JVM option: 
+Instead of the default location (`.../domain1/uploads`) we use a directory on a dedicated partition, outside of the filesystem where Dataverse is installed, via the following JVM option:
 
 ```
 <jvm-options>-Ddataverse.files.uploads=/uploads/web</jvm-options>
 ```
 
-and we have a dedicated cronjob that runs every 30 minutes and deletes everything older than 2 hours in that directory: 
+and we have a dedicated cronjob that runs every 30 minutes and deletes everything older than 2 hours in that directory:
 
 ```
 15,45 * * * * /bin/find /uploads/web/ -mmin +119 -type f -name "upload*" -exec rm -f {} \; > /dev/null 2>&1
 ```
 
-### Trailing commas in author name now permitted
+### Trailing Commas in Author Name Now Permitted
 
-When an author name ends on a comma (e.g. `Smith,` or `Smith, `), the dataset page display was broken after publishing.
-Instead, an "Error 500" page was presented to the user.
-The underlying issue causing the JSON-LD schema.org output on the page to break was fixed in #10343.
+When an author name ended in a comma (e.g. `Smith,` or `Smith, `), the dataset page was broken after publishing (a "500" error page was presented to the user). The underlying issue causing the JSON-LD Schema.org output on the page to break was fixed. See #10343 and #10776.
 
 ## API Updates
 
@@ -483,7 +481,7 @@ Below is the simplest way to reindex Solr:
 curl http://localhost:8080/api/admin/index
 ```
 
-The API above rebuilds the existing index "in place". If you want to be absolutely sure that your index is up-to-date and consistent, you may consider wiping it clean and reindexing everything from scratch (see [the guides](https://guides.dataverse.org/en/latest/admin/solr-search-index.html)). Just note that, depending on the size of your database, a full reindex may take a while and the users will be seeing incomplete search results during that window. 
+The API above rebuilds the existing index "in place". If you want to be absolutely sure that your index is up-to-date and consistent, you may consider wiping it clean and reindexing everything from scratch (see [the guides](https://guides.dataverse.org/en/latest/admin/solr-search-index.html)). Just note that, depending on the size of your database, a full reindex may take a while and the users will be seeing incomplete search results during that window.
 
 9\. Run reExportAll to update dataset metadata exports