Merge pull request #12222 from doigl/patch-2

Update 6.10-release-notes.md

Author: pdurbin

doc/release-notes/6.10-release-notes.md

@@ -10,7 +10,7 @@ This release contains major upgrades to core components. Detailed upgrade instru
 
 Highlights for Dataverse 6.10 include:
 
-- Optionally require acknowledgment of a disclaimer when publishing
+- Optionally require acknowledgement of a disclaimer when publishing
 - Optionally require embargo reason
 - Harvesting improvements
 - Croissant support now built in
@@ -22,7 +22,7 @@ Highlights for Dataverse 6.10 include:
 - New and improved APIs, including filling in a guestbook when downloading files
 - Bug fixes
 
-### Optionally Require Acknowledgment of a Disclaimer When Publishing
+### Optionally Require Acknowledgement of a Disclaimer When Publishing
 
 When users click "Publish" on a dataset they have always seen a popup displaying various information to read before clicking "Continue" to proceed with publication.
 
@@ -66,7 +66,7 @@ This release includes multiple updates to the OAI-ORE metadata export and the pr
 
 - Multiple performance and scaling improvements have been made for creating archival bags for large datasets, including:
   - The duration of archiving tasks triggered from the version table or API are no longer limited by the transaction time limit.
-  - Temporary storage space requirements have increased by `1/:BagGeneratorThreads` of the zipped bag size. (Often this is by half because the default value for `:BagGeneratorThreads` is 2.) This is a consequence of changes to avoid timeout errors on larger files/datasets.
+  - Temporary storage space requirements have been increased by `1/:BagGeneratorThreads` of the zipped bag size. (Often this is by half because the default value for `:BagGeneratorThreads` is 2.) This is a consequence of changes to avoid timeout errors on larger files/datasets.
   - The size of individual data files and the total dataset size that will be included in an archival bag can now be limited. Admins can choose whether files above these limits are transferred along with, but outside, the zipped bag (creating a complete archival copy) or are just referenced (using the concept of a "holey" bag and just listing the oversized files and the Dataverse URLs from which they can be retrieved in a `fetch.txt` file). In the holey bag case, an active service on the archiving platform must retrieve the oversized files (using appropriate credentials as needed) to make a complete copy.
   - Superusers can now see a pending status in the dataset version table while archiving is active.
   - Workflows are now triggered outside the transactions related to publication, assuring that workflow locks and status updates are always recorded.
@@ -104,7 +104,7 @@ To enable existing .qdc and .qdpx files to be used with the previewers, their co
 
 ### Review Datasets
 
-Dataverse now supports review datasets, a type of dataset that can be used to review resources such as other datasets in the Dataverse installation itself or various resources in external data repositories. APIs and a new "review" metadata block (with an "Item Reviewed" field) are in place but the UI for this feature will only available in a future version of the new React-based [Dataverse Frontend](https://github.com/IQSS/dataverse-frontend) (see [#876](https://github.com/IQSS/dataverse-frontend/pull/876)). See the [guides](https://guides.dataverse.org/en/6.10/user/dataset-management.html#review-datasets), #11747, #12015, #11887, #12115, and #11753. This feature is experimental.
+Dataverse now supports review datasets, a type of dataset that can be used to review resources such as other datasets in the Dataverse installation itself or various resources in external data repositories. APIs and a new "review" metadata block (with an "Item Reviewed" field) are in place but the UI for this feature will only be available in a future version of the new React-based [Dataverse Frontend](https://github.com/IQSS/dataverse-frontend) (see [#876](https://github.com/IQSS/dataverse-frontend/pull/876)). See the [guides](https://guides.dataverse.org/en/6.10/user/dataset-management.html#review-datasets), #11747, #12015, #11887, #12115, and #11753. This feature is experimental.
 
 ## Features Added
 
@@ -161,7 +161,7 @@ See the note above about support for REFI-QDA files. Screenshots of the previewe
 - The MyData API now supports the `metadata_fields`, `sort`, `order`, `show_collections` and `fq` parameters, which enhances its functionality and brings it in line with the Search API. See [the guides](https://guides.dataverse.org/en/6.10/api/native-api.html#mydata) and #12009.
 - This release removes an undocumented restriction on the API calls to get, set, and delete [archival status](https://guides.dataverse.org/en/6.10/api/native-api.html#get-the-archival-status-of-a-dataset-by-version). They did not work on deaccessioned dataset versions and now do. See #12065.
 - Dataset templates can be listed and deleted for a given collection (dataverse). See [the guides](https://guides.dataverse.org/en/6.10/api/native-api.html#list-single-template-by-its-identifier), #11918, and #11969. The default template can also be set. See [the guides](https://guides.dataverse.org/en/6.10/api/native-api.html#set-a-default-template-for-a-collection), #11914 and #11989.
-- Because some clients (such as the [new frontend](https://github.com/IQSS/dataverse-frontend)) need to retrieved contact email addresses along with the rest of the dataset metadata, a new query parameter called `ignoreSettingExcludeEmailFromExport` has been introduced. It requires "EditDataset" permission. See [the guides](https://guides.dataverse.org/en/6.10/api/native-api.html#get-json-representation-of-a-dataset), #11714, and #11819.
+- Because some clients (such as the [new frontend](https://github.com/IQSS/dataverse-frontend)) need to retrieve contact email addresses along with the rest of the dataset metadata, a new query parameter called `ignoreSettingExcludeEmailFromExport` has been introduced. It requires "EditDataset" permission. See [the guides](https://guides.dataverse.org/en/6.10/api/native-api.html#get-json-representation-of-a-dataset), #11714, and #11819.
 - The Change Collection Attributes API now supports `allowedDatasetTypes`. See the [guides](https://guides.dataverse.org/en/6.10/api/native-api.html#change-collection-attributes), #12115, and #11753.
 - The API returning information about datasets (`/api/datasets/{id}`) now includes a `locks` field containing a list of the types of all existing locks, e.g. `"locks": ["InReview"]`. See #12008.
 - Cleaned up Access APIs to localize getting user from session for JSF backward compatibility. This bug requires a frontend fix to send the Bearer Token in the API call. See #11740 and #11844.
@@ -224,7 +224,7 @@ We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/relea
 
 ### Hiding OIDC Provider from JSF UI
 
-This release fixes a bug where the value of the [dataverse.auth.oidc.enabled](https://guides.dataverse.org/en/6.10/installation/oidc.html#provision-via-jvm-options) setting (available when provisioning an authentication provider via JVM options) was not being not being propagated to the current Dataverse user interface (JSF, where `enabled=false` providers are not displayed for login/registration) or represented in the GET /api/admin/authenticationProviders API call.
+This release fixes a bug where the value of the [dataverse.auth.oidc.enabled](https://guides.dataverse.org/en/6.10/installation/oidc.html#provision-via-jvm-options) setting (available when provisioning an authentication provider via JVM options) was not being propagated to the current Dataverse user interface (JSF, where `enabled=false` providers are not displayed for login/registration) or represented in the GET /api/admin/authenticationProviders API call.
 
 A new JVM setting (`dataverse.auth.oidc.hidden-jsf`) was added to hide an enabled OIDC Provider from the JSF UI.
 
@@ -540,4 +540,4 @@ We also recommend you ensure you followed all update instructions from the past
 
    Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs).
 
-   If you have text customizations you can get the latest English files from <https://github.com/IQSS/dataverse/tree/v6.10/src/main/java/propertyFiles>.
+   If you have text customizations you can get the latest English files from <https://github.com/IQSS/dataverse/tree/v6.10/src/main/java/propertyFiles>.