This is an automated email from the ASF dual-hosted git repository.

rlenferink pushed a commit to branch update-getcalendar-instructions
in repository https://gitbox.apache.org/repos/asf/comdev-events-site.git

commit 65e9c5d2e21057d732f5ec9fb09c2ca513717b25
Author: Roy Lenferink <[email protected]>
AuthorDate: Wed Feb 26 18:27:23 2025 +0100

    Update instructions for manual triggering of getcalendar workflow
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 97c7405..ffc6454 100644
--- a/README.md
+++ b/README.md
@@ -30,11 +30,11 @@ Changes to the `main` branch of this repository trigger the 
[events-site Jenkins
 
 The [ASF's gitpubsub 
mechanism](https://blogs.apache.org/infra/entry/git_based_websites_available) 
then synchronizes that content to 
[https://events.apache.org/](https://events.apache.org/), usually within a few 
seconds. More details about the publication process can be found in the [ASF 
Documentation about Project sites](https://infra.apache.org/project-site.html). 
If for some reason this process fails, you can use [the self-service page from 
ASF Infra](https://selfserve.apache.org/) to [...]
 
-There is also a GitHub Action workfile that runs daily (09:20 UTC).
+There is also a GitHub Action workflow that runs daily (09:20 UTC).
 This fetches the Comdev calendar contents as a JSON file and updates the local 
copy.
-If there has been a change, this is committed to to main branch.
+If there has been a calendar change, this is committed to to main branch.
 In turn, this triggers the main site build as described above.
-The workfile can also be triggered directly if required.
+The [getcalendar.yml 
workflow](https://github.com/apache/comdev-events-site/actions/workflows/getcalendar.yml)
 can also be triggered manually if required (click the `Run workflow` button).
 
 ## Powered by Hugo!
 

Reply via email to