updated secret prefixes

Author: renatof

docs/credentials.md

@@ -3,7 +3,7 @@
 
 ## S3 data server
 
-- In general, the credentials you need from your S3 account are the `ACCESS_KEY` and the `SECRET_KEY`. These are akin to user names and passwords. 
+- In general, the credentials you need from your S3 account are the `AccessKey` and the `SecretKey`. These are akin to user names and passwords. 
 - How you obtain these credentials will depend on your provider (e.g. AWS S3, MINIO, OSN - see below)
 - Paste the access key and the secret key as _Repository secrets_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
 
@@ -32,7 +32,7 @@ In summary:
 
 - You need an API key from your provider to configure for use in FaaSr
 - How you obtain this will depend on your cloud provider.
-- Paste the API key under the name `OW_API.key` as a _Repository secret_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
+- Paste the API key under the name `OW_APIkey` as a _Repository secret_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
 
 
 ## Google Cloud

docs/defaults.md

@@ -36,7 +36,7 @@ The following values are set by default in the Web UI and take effect unless ove
 - `AWS_AccessKey`: AWS Lambda access key
 - `AWS_SecretKey`: AWS Lambda secret key
 - `GCP_SecretKey`: GCP secret key
-- `OW_API.key`: OpenWhisk API key
+- `OW_APIkey`: OpenWhisk API key
 - `SLURM_Token`: SLURM JWT token
 
 ## Log folder (in S3)

docs/workflow_repo.md

@@ -16,7 +16,14 @@ The simplest way to configure this repository is to fork from the FaaSr organiza
 - While you can choose a different name for your fork, here we assume you leave the default _FaaSr-workflow_
 - Click on the green _Create fork_ button
 
-The base repository comes with an example workflow used in the [FaaSr tutorial]
+The base repository comes with an example workflow used in the [FaaSr tutorial]. 
+
+## Enabling FaaSr actions
+
+In order to use register and invoke workflows, you also need to perform a one-time configuration to enable running the pre-defined FaaSr register and invoke workflow actions. To do this:
+
+- Click on the _Actions_ tab (top of the GitHub page, next to _Code_ and _Pull requests_)
+- Click on the green button _I understand my workflows, please go ahead and enable them_
 
 ## Configuring secrets
 
@@ -35,8 +42,8 @@ Before you can register and invoke workflows, you need to create secrets storing
 - When creating a workflow with the [FaaSr Workflow Builder Web UI], you are asked to enter a name for your S3 data server(s)
 - The default compute server name for an S3 server is `S3`
 - Assume the name of a data server you are setting the secrets for is `S3`, you need two secrets, named exactly as follows (replace `S3` with the name of the server you configured)
-- `S3_ACCESS_KEY`
-- `S3_SECRET_KEY`
+- `S3_AccessKey`
+- `S3_SecretKey`
 - The secrets you store under these names are the access and secret keys you obtained from your S3 provider
 
 ### GitHub Actions