Skip to content

DOC-3152: Fixed typos in 7.7.0 release docs and import/export word docker setup docs. #3689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kemister85 merged 1 commit into from
May 12, 2025
Merged

DOC-3152: Fixed typos in 7.7.0 release docs and import/export word docker setup docs. #3689

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ROOT/pages/7.7.0-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -372,7 +372,7 @@ This issue has been resolved in {productname} {release-version}. Input elements

This section describes issues that users of {productname} {release-version} may encounter and possible workarounds for these issues.

There one known issue in {productname} {release-version}.
There is one known issue in {productname} {release-version}.

=== Missing Hebrew translation for Blockquote toolbar button tooltip
// #TINY-11732
Expand Down
2 changes: 1 addition & 1 deletion ...xport-to-word/import-from-word-and-export-to-word-autorization-on-premises.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ To enable authorization, set the `SECRET_KEY` environment variable during the xr
If the `SECRET_KEY` variable is set, then all requests must have a header with a JWT (JSON Web Token) signed with this key. The token should be passed as a value of the `Authorization` header for each request sent to the {pluginname} REST API.

[NOTE]
If the `SECRET_KEY` is not setup during the installation, then {pluginname} On-Premises will not require any headers with tokens when sending requests to the {pluginname} REST API. However, this it is not recommend to skip the authorization when running {pluginname} On-Premises in a public network.
If the `SECRET_KEY` is not setup during the installation, then {pluginname} On-Premises will not require any headers with tokens when sending requests to the {pluginname} REST API. However, it is **not** recommended to skip the authorization when running {pluginname} On-Premises in a public network.

=== Generating the token

Expand Down