diff --git a/internal_resources/template_reference.adoc b/internal_resources/template_reference.adoc index c1ce32824d..b137278dc7 100644 --- a/internal_resources/template_reference.adoc +++ b/internal_resources/template_reference.adoc @@ -8,6 +8,6 @@ A reference module lists things (such as a list of commands) or has a very regim * A reference module that is a list of things may be made easier to scan if its content is organized alphabetically or formatted as a table. Think of an alphabetical list of commands that can be used with an application, or of an alphabetical list of system components with brief definitions formatted as a 2-column table. -* If you have a large volume of the same type of information to document, figure out a consistent structure that the information details can fit into and then doument each logical unit of information as 1 reference module. Think of man pages, which document very different information details, but that use consistent titles and formats to present those details in a consistent information structure. +* If you have a large volume of the same type of information to document, figure out a consistent structure that the information details can fit into and then document each logical unit of information as 1 reference module. Think of man pages, which document very different information details, but that use consistent titles and formats to present those details in a consistent information structure. diff --git a/release_notes/topics/10_0_0.adoc b/release_notes/topics/10_0_0.adoc index 5a84199890..3f4fea782f 100644 --- a/release_notes/topics/10_0_0.adoc +++ b/release_notes/topics/10_0_0.adoc @@ -29,7 +29,7 @@ Thanks to https://github.com/y-tabata[Yoshiyuki Tabata] A new SPI was introduced to allow better flexibility when setting security related headers on responses. This provides a cleaner implementation within Keycloak, but also allows full customisation if needed. Security headers are now set -by a response filter instead of within the code itself, which makes it less error prone, removing the chance that +by a response filter instead of within the code itself, which makes it less error-prone, removing the chance that some response are missing headers. diff --git a/release_notes/topics/15_0_1.adoc b/release_notes/topics/15_0_1.adoc index 157fdf8a1e..b42ea8e5b6 100644 --- a/release_notes/topics/15_0_1.adoc +++ b/release_notes/topics/15_0_1.adoc @@ -1,4 +1,4 @@ = Highlights -This release contains some important bug fixes. In addition, We would like to thank to https://github.com/leandrobortoli[Leandro José de Bortoli] for his contributions to the +This release contains some important bug fixes. In addition, We would like to thank https://github.com/leandrobortoli[Leandro José de Bortoli] for his contributions to the FAPI related functionalities such as JARM support and improvements in CIBA. \ No newline at end of file diff --git a/release_notes/topics/4_2_0_final.adoc b/release_notes/topics/4_2_0_final.adoc index 5ef6eaa393..3f4b5427ed 100644 --- a/release_notes/topics/4_2_0_final.adoc +++ b/release_notes/topics/4_2_0_final.adoc @@ -8,7 +8,7 @@ Thanks to https://github.com/gtudan[gtudan] for the contribution. = SAML adapter multitenancy support -The SAML adapter can support multi-tenancy now just like the built in adapter for OpenID Connect. +The SAML adapter can support multi-tenancy now just like the built-in adapter for OpenID Connect. = An option to create claims with dots (.) in them diff --git a/release_notes/topics/4_3_0_final.adoc b/release_notes/topics/4_3_0_final.adoc index 95c249415b..fb8c65dcc7 100644 --- a/release_notes/topics/4_3_0_final.adoc +++ b/release_notes/topics/4_3_0_final.adoc @@ -16,7 +16,7 @@ the Keycloak Server validates Subject DN field of the client's certificate. For this release, we improved policy evaluation performance across the board, increasing reliability and throughput. The main changes we did were related with trying to optimize the policy evaluation path by avoiding unnecessary flows and collect decisions -as soon as they happen. We also introduced a policy decision cache on a per request basis, avoiding redundant decisions from policies +as soon as they happen. We also introduced a policy decision cache on a per-request basis, avoiding redundant decisions from policies previously evaluated. We are also working on other layers of cache which should give a much better experience. See https://issues.redhat.com/browse/KEYCLOAK-7952[KEYCLOAK-7952]. diff --git a/release_notes/topics/4_5_0_final.adoc b/release_notes/topics/4_5_0_final.adoc index f067f79aa3..9512784332 100644 --- a/release_notes/topics/4_5_0_final.adoc +++ b/release_notes/topics/4_5_0_final.adoc @@ -2,7 +2,7 @@ The Signature SPI makes it possible to plug-in additional signature algorithms. This enables additional signatures and also enables changing how signatures are generated. For example, using this allows using an HSM device to sign tokens. -Thanks to https://github.com/tnorimat[tnorimat] for contributing a signficant part of this work. +Thanks to https://github.com/tnorimat[tnorimat] for contributing a significant part of this work. = New Signature Algorithms @@ -17,7 +17,7 @@ HMAC (HS256/384/512) are also very useful when you do not want your application Since these are symmetric signatures only Keycloak is able to verify the signature, which requires the application to use the token introspection endpoint to verify tokens. -Thanks to https://github.com/tnorimat[tnorimat] for contributing a signficant part of this work. +Thanks to https://github.com/tnorimat[tnorimat] for contributing a significant part of this work. = Better Audience Support for OpenID Connect clients diff --git a/release_notes/topics/8_0_0.adoc b/release_notes/topics/8_0_0.adoc index 8210242ee4..3910e829be 100644 --- a/release_notes/topics/8_0_0.adoc +++ b/release_notes/topics/8_0_0.adoc @@ -27,7 +27,7 @@ Message bundles in theme resources enables internationalization of custom provid We have added a new SPI that allows for the configuration of custom role mappers that are used by the SAML adapters to map the roles extracted from the SAML assertion into roles that exist in the SP application environment. This is particularly useful when the adapters need to communicate with third party IDPs and the roles set by the IDP in the assertion do not correspond to -the roles that were defined for the SP application. The provider to be used can configured in the `keycloak-saml.xml` +the roles that were defined for the SP application. The provider to be used can be configured in the `keycloak-saml.xml` file or in the `keycloak-saml` subsystem. An implementation that performs the role mappings based on the contents of a properties file was also provided. diff --git a/release_notes/topics/8_0_2.adoc b/release_notes/topics/8_0_2.adoc index f984c9be9d..3d97ab68f3 100644 --- a/release_notes/topics/8_0_2.adoc +++ b/release_notes/topics/8_0_2.adoc @@ -5,5 +5,5 @@ Starting with version 80, Google Chrome will change the default value for the `SameSite` cookie parameter to `Lax`. Therefore, changes were required to several {project_name} cookies (especially those which are used within the Javascript adapter for checking the session status using the iframe) to set `SameSite` parameter to `None`. Please note -that this settings also requires setting the `Secure` parameter, hence starting with this version, the Javascript +that this setting also requires setting the `Secure` parameter, hence starting with this version, the Javascript adapter will only be fully functional when using the SSL / TLS connection on the {project_name} side. \ No newline at end of file diff --git a/release_notes/topics/9_0_1.adoc b/release_notes/topics/9_0_1.adoc index 91b38c45ce..662739523e 100644 --- a/release_notes/topics/9_0_1.adoc +++ b/release_notes/topics/9_0_1.adoc @@ -11,7 +11,7 @@ applications from the legacy/deprecated API to the native promise API. == Reverted breaking API changes to LocaleSelectorSPI In 9.0.0 a breaking API change was introduced to LocaleSelectorSPI. With 9.0.1 the changes to -this API is now reverted, and a new LocaleUpdatorSPI has been introduced. +this API is now reverted, and a new LocaleUpdaterSPI has been introduced. == Fixed the automatic resolution of `KeycloakConfigResolver` instances for Spring Boot Applications @@ -19,4 +19,4 @@ In previous releases, Spring Boot applications had to manually implement the `Ke built-in `org.keycloak.adapters.springboot.KeycloakSpringBootConfigResolver`. This release fixes the backward compatibility issue by resolving instances automatically in case none is provided. As well as still -allowing applications to provide their own configuration resolver implementations. \ No newline at end of file +allowing applications to provide their own configuration resolver implementations. diff --git a/release_notes/topics/product/7_3_final.adoc b/release_notes/topics/product/7_3_final.adoc index 83eb68278a..8e243b8420 100644 --- a/release_notes/topics/product/7_3_final.adoc +++ b/release_notes/topics/product/7_3_final.adoc @@ -6,7 +6,7 @@ The following notes apply to the RH-SSO 7.3 release. = New or Improved Features -Some of the new features in this release are technology preview features, which means they are available, but not fully supported. You may use these for testing, but features marked for technology preview are not supported for use in production. These are marked as technology preview in this list and in our documentation. Because they are not fully supported for production use, technology preview features are disabled by default, but the features can be enabled if you want to try them out. We are seeking feedback on the technology preview features, so please log a support ticket if you have comments on a technology preview feature. Once a feature transitions from technology preview to production supported, the API and functionality are fixed for the lifecyle of the major version, so comments during the tech preview period are critical to influencing a feature in the way you want. +Some of the new features in this release are technology preview features, which means they are available, but not fully supported. You may use these for testing, but features marked for technology preview are not supported for use in production. These are marked as technology preview in this list and in our documentation. Because they are not fully supported for production use, technology preview features are disabled by default, but the features can be enabled if you want to try them out. We are seeking feedback on the technology preview features, so please log a support ticket if you have comments on a technology preview feature. Once a feature transitions from technology preview to production supported, the API and functionality are fixed for the lifecycle of the major version, so comments during the tech preview period are critical to influencing a feature in the way you want. Existing features that remain in tech preview in this release include: @@ -56,7 +56,7 @@ Features marked for technology preview are not supported for use in production. == New Capabilities in Client Adapters -* Fuse 7 - Fuse adapter aligned with latest Fuse 7 release +* Fuse 7 - Fuse adapter aligned with the latest Fuse 7 release * Sprint Boot 2 support