Skip to content

Commit 0b9652d

Browse files
committed
JFrog article fixes
1 parent 5b6d31b commit 0b9652d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-jfrog.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To use OIDC with JFrog, establish a trust relationship between {% data variables
4848

4949
## Updating your {% data variables.product.prodname_actions %} workflow
5050

51-
Once your trusted is established on your JFrog Platform, you can update your {% data variables.product.prodname_actions %} workflow to work on the JFrog platform.
51+
Once you establish a trust relationship between {% data variables.product.prodname_actions %} and the JFrog platform, you can update your {% data variables.product.prodname_actions %} workflow.
5252

5353
In your {% data variables.product.prodname_actions %} workflow file, ensure you are using the provider name and audience you configured in the JFrog Platform.
5454

@@ -69,7 +69,7 @@ The following example uses the placeholder `YOUR_PROVIDER_NAME`.
6969
echo ACCESS_TOKEN=$ACCESS_TOKEN >> $GITHUB_OUTPUT
7070
```
7171

72-
The following example uses the placeholder `YOUR_AUDIENCE` with cURL.
72+
The following example show part of a {% data variables.product.prodname_actions %} workflow file using cURL.
7373

7474
```yaml
7575
- name: Get ID Token (cURL method)

0 commit comments

Comments
 (0)