docs: update usage of its

gravitational · Jan 9, 2025 · b488116 · b488116
1 parent c60241b
commit b488116
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/pages/admin-guides/access-controls/idps/saml-attribute-mapping.mdx b/docs/pages/admin-guides/access-controls/idps/saml-attribute-mapping.mdx
@@ -73,7 +73,7 @@ Attribute mapping that points to a non-existent value will not be included in SA
 Predicate expressions for attribute mapping are evaluated against user attributes that can be accessed using
 evaluation context listed above.
 
-The supported functions and methods are listed below, along with the usage syntax and it's result, evaluated 
+The supported functions and methods are listed below, along with the usage syntax and its result, evaluated 
 against the following reference user spec file:
 ```yaml
 # reference user spec file
@@ -200,4 +200,4 @@ $ tctl idp saml test-attribute-mapping --user user.yml --sp sp.yml
 Print result in format of choice.
 ```code
 $ tctl idp saml test-attribute-mapping --user user.yml --sp sp.yml --format (json/yaml)
-```
+```
diff --git a/docs/pages/admin-guides/access-controls/idps/saml-guide.mdx b/docs/pages/admin-guides/access-controls/idps/saml-guide.mdx
@@ -141,7 +141,7 @@ $ tctl create iamshowcase.yaml
 </Details>
 
 <Admonition type="important">
-If an `entity_descriptor` is provided, it's content takes preference over values provided in `entity_id` and `acs_url`.
+If an `entity_descriptor` is provided, its content takes preference over values provided in `entity_id` and `acs_url`.
 
 Teleport only tries to fetch or generate entity descriptor when service provider is created for the first time.
 Subsequent updates require an entity descriptor to be present in the service provider spec. As such, when updating

diff --git a/docs/pages/reference/architecture/trustedclusters.mdx b/docs/pages/reference/architecture/trustedclusters.mdx
@@ -29,7 +29,7 @@ databases behind a firewall.
 In the example below, there are three independent clusters:
 
 - Cluster `sso.example.com` is a root cluster. This cluster can be used as a single-sign-on entry point
-for your organization. It can have it's own independent resources connected to it, or be used just for audit
+for your organization. It can have its own independent resources connected to it, or be used just for audit
 logs collection and single-sign-on.
 - Clusters `us-east-1a` and `us-east-1b` are two independent clusters in different availability zones.