Skip to content
This repository was archived by the owner on Apr 19, 2023. It is now read-only.

Commit 33baeef

Browse files
authored
Fix minor typos in the 'Release Notes' guide (#1705)
1 parent 8f6aee0 commit 33baeef

File tree

10 files changed

+13
-13
lines changed

10 files changed

+13
-13
lines changed

internal_resources/template_reference.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@ A reference module lists things (such as a list of commands) or has a very regim
88

99
* 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.
1010

11-
* 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.
11+
* 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.
1212

1313

release_notes/topics/10_0_0.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Thanks to https://github.com/y-tabata[Yoshiyuki Tabata]
2929

3030
A new SPI was introduced to allow better flexibility when setting security related headers on responses. This provides
3131
a cleaner implementation within Keycloak, but also allows full customisation if needed. Security headers are now set
32-
by a response filter instead of within the code itself, which makes it less error prone, removing the chance that
32+
by a response filter instead of within the code itself, which makes it less error-prone, removing the chance that
3333
some response are missing headers.
3434

3535

release_notes/topics/15_0_1.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
= Highlights
22

3-
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
3+
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
44
FAPI related functionalities such as JARM support and improvements in CIBA.

release_notes/topics/4_2_0_final.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Thanks to https://github.com/gtudan[gtudan] for the contribution.
88

99
= SAML adapter multitenancy support
1010

11-
The SAML adapter can support multi-tenancy now just like the built in adapter for OpenID Connect.
11+
The SAML adapter can support multi-tenancy now just like the built-in adapter for OpenID Connect.
1212

1313

1414
= An option to create claims with dots (.) in them

release_notes/topics/4_3_0_final.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ the Keycloak Server validates Subject DN field of the client's certificate.
1616

1717
For this release, we improved policy evaluation performance across the board, increasing reliability and throughput. The main
1818
changes we did were related with trying to optimize the policy evaluation path by avoiding unnecessary flows and collect decisions
19-
as soon as they happen. We also introduced a policy decision cache on a per request basis, avoiding redundant decisions from policies
19+
as soon as they happen. We also introduced a policy decision cache on a per-request basis, avoiding redundant decisions from policies
2020
previously evaluated.
2121

2222
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].

release_notes/topics/4_5_0_final.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
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.
44

5-
Thanks to https://github.com/tnorimat[tnorimat] for contributing a signficant part of this work.
5+
Thanks to https://github.com/tnorimat[tnorimat] for contributing a significant part of this work.
66

77
= New Signature Algorithms
88

@@ -17,7 +17,7 @@ HMAC (HS256/384/512) are also very useful when you do not want your application
1717
Since these are symmetric signatures only Keycloak is able to verify the signature, which requires the
1818
application to use the token introspection endpoint to verify tokens.
1919

20-
Thanks to https://github.com/tnorimat[tnorimat] for contributing a signficant part of this work.
20+
Thanks to https://github.com/tnorimat[tnorimat] for contributing a significant part of this work.
2121

2222
= Better Audience Support for OpenID Connect clients
2323

release_notes/topics/8_0_0.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Message bundles in theme resources enables internationalization of custom provid
2727
We have added a new SPI that allows for the configuration of custom role mappers that are used by the SAML adapters to map
2828
the roles extracted from the SAML assertion into roles that exist in the SP application environment. This is particularly useful
2929
when the adapters need to communicate with third party IDPs and the roles set by the IDP in the assertion do not correspond to
30-
the roles that were defined for the SP application. The provider to be used can configured in the `keycloak-saml.xml`
30+
the roles that were defined for the SP application. The provider to be used can be configured in the `keycloak-saml.xml`
3131
file or in the `keycloak-saml` subsystem. An implementation that performs the role mappings based on the contents of a properties
3232
file was also provided.
3333

release_notes/topics/8_0_2.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,5 @@
55
Starting with version 80, Google Chrome will change the default value for the `SameSite` cookie parameter to `Lax`.
66
Therefore, changes were required to several {project_name} cookies (especially those which are used within the
77
Javascript adapter for checking the session status using the iframe) to set `SameSite` parameter to `None`. Please note
8-
that this settings also requires setting the `Secure` parameter, hence starting with this version, the Javascript
8+
that this setting also requires setting the `Secure` parameter, hence starting with this version, the Javascript
99
adapter will only be fully functional when using the SSL / TLS connection on the {project_name} side.

release_notes/topics/9_0_1.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ applications from the legacy/deprecated API to the native promise API.
1111
== Reverted breaking API changes to LocaleSelectorSPI
1212

1313
In 9.0.0 a breaking API change was introduced to LocaleSelectorSPI. With 9.0.1 the changes to
14-
this API is now reverted, and a new LocaleUpdatorSPI has been introduced.
14+
this API is now reverted, and a new LocaleUpdaterSPI has been introduced.
1515

1616
== Fixed the automatic resolution of `KeycloakConfigResolver` instances for Spring Boot Applications
1717

1818
In previous releases, Spring Boot applications had to manually implement the `KeycloakConfigResolver` interface or extend the
1919
built-in `org.keycloak.adapters.springboot.KeycloakSpringBootConfigResolver`.
2020

2121
This release fixes the backward compatibility issue by resolving instances automatically in case none is provided. As well as still
22-
allowing applications to provide their own configuration resolver implementations.
22+
allowing applications to provide their own configuration resolver implementations.

release_notes/topics/product/7_3_final.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The following notes apply to the RH-SSO 7.3 release.
66

77
= New or Improved Features
88

9-
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.
9+
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.
1010

1111
Existing features that remain in tech preview in this release include:
1212

@@ -56,7 +56,7 @@ Features marked for technology preview are not supported for use in production.
5656

5757
== New Capabilities in Client Adapters
5858

59-
* Fuse 7 - Fuse adapter aligned with latest Fuse 7 release
59+
* Fuse 7 - Fuse adapter aligned with the latest Fuse 7 release
6060

6161
* Sprint Boot 2 support
6262

0 commit comments

Comments
 (0)