This is an automated email from the ASF dual-hosted git repository.
sbp pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
The following commit(s) were added to refs/heads/main by this push:
new d389573 Fix a couple of small documentation issues
d389573 is described below
commit d389573d3cf1e0ccdd64cb9cf234fe36d2393f08
Author: Sean B. Palmer <[email protected]>
AuthorDate: Fri Jan 23 15:11:59 2026 +0000
Fix a couple of small documentation issues
---
atr/docs/input-validation.md | 2 +-
atr/docs/security-authorization.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/atr/docs/input-validation.md b/atr/docs/input-validation.md
index 5e232a3..744850c 100644
--- a/atr/docs/input-validation.md
+++ b/atr/docs/input-validation.md
@@ -102,7 +102,7 @@ In templates, include the CSRF token in every form:
</form>
```
-The CSRF token is tied to the user's session and validated on form submission.
Requests without a valid CSRF token are rejected.
+The CSRF token is tied to the user's session and validated on form submission.
Requests without a valid CSRF token are rejected. When using the form module
renderer, the CSRF token is added automatically.
## Validation rules by input type
diff --git a/atr/docs/security-authorization.md
b/atr/docs/security-authorization.md
index d71bcd6..9d76df1 100644
--- a/atr/docs/security-authorization.md
+++ b/atr/docs/security-authorization.md
@@ -39,7 +39,7 @@ ATR recognizes the following roles, derived from ASF LDAP:
* **Committer**: Any authenticated ASF committer. Can create Personal Access
Tokens and view their own committees and projects. Determined by existence in
LDAP `ou=people,dc=apache,dc=org`.
-* **Project Participant**: A committer who is a member of a specific project
(has commit access). Can start releases, upload artifacts, and cast votes for
that project. Determined by the `member` attribute in the project's LDAP group.
+* **Project Participant**: A committer who is a member of a specific project.
Can start releases, upload artifacts, and cast votes for that project.
Determined by the `member` attribute in the project's LDAP group.
* **PMC Member**: A committer who is on the PMC (Project Management Committee)
for a specific committee. Has all participant permissions plus can resolve
votes, finish releases, configure project settings, and manage signing keys.
Determined by the `owner` attribute in the committee's LDAP group.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]