diff --git a/README.md b/README.md index c6cc617..afc4d0c 100644 --- a/README.md +++ b/README.md @@ -587,11 +587,11 @@ client's limits by tag. See "Request tags" in [`SPEC.md`](SPEC.md). - These apps work out of the box at the default settings, and their recorded ordinary requests pass the Core Rule Set: - gitea: git over HTTP and sign-in through Git Credential Manager get - through. On gitea's own paths, its searches, file names and branch names - do too. + through. On gitea's own paths, its searches, file names, branch names and + repository names do too. - Forgejo: git over HTTP and its container and package registries get - through. On Forgejo's own paths, its searches, file names and branch names - do too. + through. On Forgejo's own paths, its searches, file names, branch names + and repository names do too. - WordPress: saving a post from the block editor gets through. On WordPress's own paths, its searches, names and file names do too. - Drupal: on Drupal's own paths, the page to return to, its searches and its diff --git a/SPEC.md b/SPEC.md index c98afe0..746bde8 100644 --- a/SPEC.md +++ b/SPEC.md @@ -812,9 +812,9 @@ The changes hold in front of every app, and no setting undoes them: a push reuses a layer, `from` names the image the layer comes from. An image such as `owner/python3-app` would have that push refused. 8. On gitea's paths, some fields skip the rules that refused ordinary gitea - requests there. They are the fields where gitea sends a search, a file name - or a branch name. `internal/coreruleset/gitea.conf` lists each rule and the - request it refused. The fields are: + requests there. They are the fields where gitea sends a search, a file name, + a branch name or a repository's name. `internal/coreruleset/gitea.conf` lists + each rule and the request it refused. The fields are: - `q` on gitea's searches of code, of issues and pull requests, and of commits. A code search holds code, such as `