opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-09-19 01:58:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: spelling fixes (#67684)

Browse Source 
This commit fixes various spelling errors throughout the docs
This commit is contained in:
Travis Rodgers
2026-06-11 13:36:50 +00:00
committed by GitHub
parent 5db931b71b
commit 0ca10ce2a3
6 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/identity-governance/access-requests/plugins/email.mdx
+2 -2
View File
@@ -351,13 +351,13 @@ Request event by using the `delivery.recipients` field:
<TabItem label="Executable or Docker">
```toml
[delivery]
recipients = ["eng@exmaple.com", "dev@example.com"]
recipients = ["eng@example.com", "dev@example.com"]
```
</TabItem>
<TabItem label="Helm Chart">
```yaml
delivery:
recipients: ["eng@exmaple.com", "dev@example.com"]
recipients: ["eng@example.com", "dev@example.com"]
```
</TabItem>
</Tabs>
docs/pages/includes/config-reference/auth-service.yaml
+1 -1
View File
@@ -513,7 +513,7 @@ auth_service:
# (Optional) Athena workgroup used by access monitoring queries (if not set, the default primary workgroup will be used).
workgroup: access_monitoring_workgroup
# Enables storing CAs in an external Hardware Security Module(HSM) or Key Management Service(KMS)
# Only one of the options can be enbabled at a given time.
# Only one of the options can be enabled at a given time.
ca_key_params:
# Persist CAs to Google Cloud KMS.
gcp_kms:
docs/pages/includes/discovery/discovery-config.yaml
+1 -1
View File
@@ -97,7 +97,7 @@ discovery_service:
http_proxy: http://172.31.5.130:3128
no_proxy: my-local-domain
# Optional section: ssm is used to configure which AWS SSM document to use
# If the ssm section isnt provided the below defaults are used.
# If the ssm section isn't provided the below defaults are used.
ssm:
# document_name is the name of the SSM document that should be
# executed when installing teleport on matching nodes
docs/pages/includes/provision-token/github-spec.mdx
+1 -1
View File
@@ -71,7 +71,7 @@ spec:
# be empty.
environment: production
# actor is the GitHub username that caused the GitHub Actions run,
# whether by committing or by directly despatching the workflow.
# whether by committing or by directly dispatching the workflow.
actor: octocat
# ref is the git ref that triggered the action run.
ref: refs/heads/main
docs/pages/reference/architecture/agents.mdx
+1 -1
View File
@@ -81,7 +81,7 @@ with periodic ping messages. Clients can access the list of all agent instances
in their cluster via the Auth Service API or CLI.
An agent's identity is represented by SSH host certificate it receives after
registering withing the cluster:
registering within the cluster:
![Host certificate](../../../img/architecture/ssh-host-cert@1.2x.svg)
docs/pages/zero-trust-access/sso/integrate-idp/oidc.mdx
+1 -1
View File
@@ -171,7 +171,7 @@ callback invalid.
In addition, Teleport supports OIDC provider specific ACR value processing
which can be enabled by setting the `provider` field in OIDC configuration. At
the moment, the only build-in support is for NetIQ.
the moment, the only built-in support is for NetIQ.
A example of using ACR values and provider specific processing is below: