From 4f6dac39c86edae447cffbc1ba268ea1b89e80a0 Mon Sep 17 00:00:00 2001 From: Paul Gottschling Date: Tue, 29 Oct 2024 14:46:16 -0400 Subject: [PATCH] Fix grammar in the Usage/Billing guide --- docs/pages/usage-billing.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/usage-billing.mdx b/docs/pages/usage-billing.mdx index 3465c5a84bbc7..fd35fd8e8e048 100644 --- a/docs/pages/usage-billing.mdx +++ b/docs/pages/usage-billing.mdx @@ -126,7 +126,7 @@ which starts on the subscription start date and ends on each monthly anniversary thereafter. If you recreate a single resource more than once an hour, this will affect the -hourly average. For example, if were to create then delete 10 servers three +hourly average. For example, if you were to create then delete 10 servers three times in one hour, Teleport would display 10 servers at any given time. However, for the entire hour, Teleport would report 30 protected servers. @@ -184,7 +184,7 @@ In Teleport, single sign-on (SSO) users are when its session expires. To count the number of SSO users in your cluster, you can examine Teleport audit events for unique SSO users that have authenticated to Teleport during a given time period. The Teleport documentation includes -[how-to guides](./admin-guides/management/export-audit-events/export-audit-events.mdx) for +[how-to guides](./admin-guides/management/export-audit-events.mdx) for exporting audit events to common log management solutions so you can identify users that have authenticated using an SSO provider.