wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update typos action and fix typos (#1661)

Browse source 
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2023-10-11 12:42:05 +02:00 • committed by GitHub
parent 560d98ba9b
commit 9fe119370b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
9 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
meta/documentation_style.rst
View file

@ -191,4 +191,4 @@ Describing grammar
Use `RFC5234-style ABNF <https://datatracker.ietf.org/doc/html/rfc5234>`_ when describing
the grammar for something in the spec, such as user IDs or server names. Use lowercase
and underscore-deliminated element names (`user_id`, not `UserID` or `user-id`).
and underscore-delimited element names (`user_id`, not `UserID` or `user-id`).

2
meta/releasing.md
View file

@ -31,7 +31,7 @@ day until the release has actually happened & blog post published.
Once a release is scheduled, the SCT will begin planning what the next release is
expected to look like. The plan should be included in the spec release blog post,
and be ready for exeuction on spec release day. Plans are guides and not promises.
and be ready for execution on spec release day. Plans are guides and not promises.
A blog post for the SCT members to review should be ready at minimum 1 week before
the target release date. 1-2 days before the release itself, the prerequisite steps