This is an automated email from the ASF dual-hosted git repository.
lprimak pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shiro-site.git
The following commit(s) were added to refs/heads/main by this push:
new 19c7c9b21 chore: fix spelling (#231)
19c7c9b21 is described below
commit 19c7c9b21b50156ce1c7900233a54b16d418c3be
Author: John Bampton <[email protected]>
AuthorDate: Tue Jul 1 08:16:30 2025 +1000
chore: fix spelling (#231)
---
CONTRIBUTING.adoc | 2 +-
src/site/content/architecture.adoc | 2 +-
src/site/content/cas.adoc | 8 ++++----
src/site/content/community.adoc | 2 +-
src/site/content/jakarta-ee.adoc | 2 +-
src/site/content/testing.adoc | 2 +-
src/site/templates/download.ftl | 6 +++---
src/site/templates/index.ftl | 2 +-
8 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/CONTRIBUTING.adoc b/CONTRIBUTING.adoc
index eb663d8ac..12abbf709 100644
--- a/CONTRIBUTING.adoc
+++ b/CONTRIBUTING.adoc
@@ -56,7 +56,7 @@ After modifying the artifacts file, update the `releases`
object in link:data/re
Look for hard coded versions and replace them.
Unfortunately, JBake does not allow custom types.
-For this reason, templating is not availble for `.htaccess` files.
+For this reason, templating is not available for `.htaccess` files.
== Development server
diff --git a/src/site/content/architecture.adoc
b/src/site/content/architecture.adoc
index f20d37f0f..47babd9a0 100644
--- a/src/site/content/architecture.adoc
+++ b/src/site/content/architecture.adoc
@@ -62,7 +62,7 @@ The `SessionDAO` performs `Session` persistence (CRUD)
operations on behalf of t
The `CacheManager` creates and manages `Cache` instance lifecycles used by
other Shiro components. Because Shiro can access many back-end data sources for
authentication, authorization and session management, caching has always been a
first-class architectural feature in the framework to improve performance while
using these data sources. Any of the modern open-source and/or enterprise
caching products can be plugged in to Shiro to provide a fast and efficient
user-experience.
* *Cryptography*
(link:static/current/apidocs/shiro-crypto-cipher/org/apache/shiro/crypto/cipher/package-summary.html[org.apache.shiro.crypto.cipher.*])
-Cryptography is a natural addition to an enterprise security framework.
Shiro's `crypto` package contains easy-to-use and understand representations of
crytographic Ciphers, Hashes (aka digests) and different codec implementations.
All the classes in this package are carefully designed to be very easy to use
and easy to understand. Anyone who has used Java's native cryptography support
knows it can be a challenging animal to tame. Shiro's crypto APIs simplify the
complicated Java mechani [...]
+Cryptography is a natural addition to an enterprise security framework.
Shiro's `crypto` package contains easy-to-use and understand representations of
cryptographic Ciphers, Hashes (aka digests) and different codec
implementations. All the classes in this package are carefully designed to be
very easy to use and easy to understand. Anyone who has used Java's native
cryptography support knows it can be a challenging animal to tame. Shiro's
crypto APIs simplify the complicated Java mechan [...]
* *Realms*
(link:static/current/apidocs/org/apache/shiro/realm/Realm.html[org.apache.shiro.realm.Realm])
As mentioned above, Realms act as the ‘bridge’ or
‘connector’ between Shiro and your application’s security
data. When it comes time to actually interact with security-related data like
user accounts to perform authentication (login) and authorization (access
control), Shiro looks up many of these things from one or more Realms
configured for an application. You can configure as many `Realms` as you need
(usually one per data source) and Shiro will coordinat [...]
diff --git a/src/site/content/cas.adoc b/src/site/content/cas.adoc
index 570eb8e76..a3bb6328c 100644
--- a/src/site/content/cas.adoc
+++ b/src/site/content/cas.adoc
@@ -101,8 +101,8 @@ casRealm.casService =
http://application.examples.com/shiro-cas
----
The _casServerUrlPrefix_ is the url of the CAS server (for example:
https://server.cas.com).
-The _casService_ is the application service url, the url on wich the
application receives CAS service ticket (for example:
http://application.examples.com/shiro-cas).
-The _validationProcol_ can be SAML or CAS (default): attributes and remember
me information are only pushed throught the SAML validation procotol (except
specific customizations). It depends on the version of the CAS server: SAML
protocol can be used with CAS server version >= 3.1.
+The _casService_ is the application service url, the url on which the
application receives CAS service ticket (for example:
http://application.examples.com/shiro-cas).
+The _validationProcol_ can be SAML or CAS (default): attributes and remember
me information are only pushed through the SAML validation protocol (except
specific customizations). It depends on the version of the CAS server: SAML
protocol can be used with CAS server version >= 3.1.
[CAUTION]
====
@@ -116,7 +116,7 @@ If you choose SAML validation, you need some more specific
dependencies:
The _defaultRoles_ is the default roles given to the authenticated user after
CAS authentication success.
The _defaultPermissions_ is the default permissions given to the authenticated
user after CAS authentication success.
The _roleAttributeNames_ defines the names of the attributes received from CAS
response which define roles to give to the authenticated user (the roles are
separated by comas).
-The _permissionAttributeNames_ defines the names of the attributes received
from CAS response which define permissions to give to the autnewhenticated user
(the permissions are separated by comas).
+The _permissionAttributeNames_ defines the names of the attributes received
from CAS response which define permissions to give to the authenticated user
(the permissions are separated by comas).
=== CasSubjectFactory
@@ -151,7 +151,7 @@ And the login url if the user is not authenticated is to be
defined on the CAS s
roles.loginUrl =
https://server.cas.com/login?service=http://application.examples.com/shiro-cas
----
-This way, if you are not authenticated and try to acces a _/protected/**_ url,
you are redirected to the CAS server for authentication.
+This way, if you are not authenticated and try to access a _/protected/**_
url, you are redirected to the CAS server for authentication.
=== Complete configuration sample
diff --git a/src/site/content/community.adoc b/src/site/content/community.adoc
index ed9cb319a..06558e002 100644
--- a/src/site/content/community.adoc
+++ b/src/site/content/community.adoc
@@ -23,7 +23,7 @@ Our community is here to help you learn about Shiro, figure
out how to do what y
Apache Shiro is a non-profit project and relies on your help and contributions
in order to evolve and improve.
-At the Shiro project we make it easy for anyone to join our great community
and lend a hand. We welcome any help you can offer inlcuding help with
documentation, identifying bugs, providing answers on the user mailing list,
and providing helpful code improvements.
+At the Shiro project we make it easy for anyone to join our great community
and lend a hand. We welcome any help you can offer including help with
documentation, identifying bugs, providing answers on the user mailing list,
and providing helpful code improvements.
* *link:how-to-contribute.html[How to Contribute]* - Join our community and
help make Apache Shiro even better
diff --git a/src/site/content/jakarta-ee.adoc b/src/site/content/jakarta-ee.adoc
index 3d3c0ae75..6cf77973a 100644
--- a/src/site/content/jakarta-ee.adoc
+++ b/src/site/content/jakarta-ee.adoc
@@ -308,7 +308,7 @@ Jakarta EE module will automatically resubmit forms when
session expires and a s
<param-value>true</param-value>
</context-param>
----
-During form resubmissions, the original request is replayed, and the response
is relayed back to the browser, along with any cookies genereated. Cookies are
set to be secure by default.
+During form resubmissions, the original request is replayed, and the response
is relayed back to the browser, along with any cookies generated. Cookies are
set to be secure by default.
[source,xml]
.To disable secure cookie attribute, add the following to `web.xml`:
----
diff --git a/src/site/content/testing.adoc b/src/site/content/testing.adoc
index 9dc3e3938..78e446893 100644
--- a/src/site/content/testing.adoc
+++ b/src/site/content/testing.adoc
@@ -189,7 +189,7 @@ How long you keep the subject bound to the thread (or swap
it out for a new inst
The `tearDownSubject()` method in the example uses a Junit 4 annotation to
ensure that the Subject is cleared from the thread after every test method is
executed, no matter what. This requires you to set up a new `Subject` instance
and set it (via `setSubject`) for every test that executes.
-This is not strictly necessary, however. For example, you could just bind a
new Subject instance (via `setSujbect`) at the beginning of every test, say, in
an `@Before`-annotated method. But if you're going to do that, you might as
well have the `@After tearDownSubject()` method to keep things symmetrical and
'clean'.
+This is not strictly necessary, however. For example, you could just bind a
new Subject instance (via `setSubject`) at the beginning of every test, say, in
an `@Before`-annotated method. But if you're going to do that, you might as
well have the `@After tearDownSubject()` method to keep things symmetrical and
'clean'.
You can mix and match this setup/teardown logic in each method manually or use
the @Before and @After annotations as you see fit. The `AbstractShiroTest`
super class will however unbind the Subject from the thread after all tests
because of the `@AfterClass` annotation in its `tearDownShiro()` method.
diff --git a/src/site/templates/download.ftl b/src/site/templates/download.ftl
index 1ec8179f8..543a48227 100644
--- a/src/site/templates/download.ftl
+++ b/src/site/templates/download.ftl
@@ -15,13 +15,13 @@
<#assign displayReleases=((content.releases).versions)![] />
<#assign downloadUrl="https://www.apache.org/dyn/closer.lua/shiro/"; />
<#assign appendToGpg=".txt" />
- <#assign buildRequitements="The source bundle requires JDK 11+ and Maven
3.8+ to build:"/>
+ <#assign buildRequirements="The source bundle requires JDK 11+ and Maven
3.8+ to build:"/>
<#else>
<#-- if not releases are given using :jbake-release:, assume oldReleases
(release-archive.html). -->
<#assign displayReleases=versions.oldReleases />
<#assign downloadUrl="https://archive.apache.org/dist/shiro/"; />
<#assign appendToGpg="" />
- <#assign buildRequitements="The source bundle requires JDK 1.8 and Maven
3.0.3+ to build:"/>
+ <#assign buildRequirements="The source bundle requires JDK 1.8 and Maven
3.0.3+ to build:"/>
</#if>
<#assign downloadHashUrl="https://downloads.apache.org/shiro/"; />
@@ -48,7 +48,7 @@
<h3 id="${release.version?replace(".", "")}Source">${release.version} Source
Code Distribution</h3>
- <p>${buildRequitements}
+ <p>${buildRequirements}
<code><a class="external-link"
href="${downloadUrl}${release.version}/shiro-root-${release.version}-source-release.zip">shiro-root-${release.version}-source-release.zip</a></code>
(<a class="external-link"
diff --git a/src/site/templates/index.ftl b/src/site/templates/index.ftl
index be4b00bbd..83ab22675 100644
--- a/src/site/templates/index.ftl
+++ b/src/site/templates/index.ftl
@@ -92,7 +92,7 @@
<h2 class="panel-title"> Integrations</h2>
</div>
<div class="card-body shadow-sm pb-2">
- <p>API’s giving you power and simplicty beyond what Java
provides by default...</p>
+ <p>API’s giving you power and simplicity beyond what Java
provides by default...</p>
<a href="<#if
(content.rootpath)??>${content.rootpath}<#else></#if>integration.html"><span
class="more">Read More >>></span></a>
</div>
</div>
