From 19953299d6fa62f7f05012ada0a7add29c695af6 Mon Sep 17 00:00:00 2001
From: Andy Miller <48326098+amiller-ims@users.noreply.github.com>
Date: Thu, 9 Nov 2023 22:51:49 +0900
Subject: [PATCH] Fix typos in recommended-practices.md

Two occurrences of "standars" instead of "standards"
---
 ob_v3p0/impl/recommended-practices.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ob_v3p0/impl/recommended-practices.md b/ob_v3p0/impl/recommended-practices.md
index 196dc308..5eb9fa59 100644
--- a/ob_v3p0/impl/recommended-practices.md
+++ b/ob_v3p0/impl/recommended-practices.md
@@ -463,7 +463,7 @@ data.
 #### Key provenance
 
 Keys used in proof generation must belong to the issuer. However, there isn't
-a existing way in current standars to completely assure this provenance.
+a existing way in current standards to completely assure this provenance.
 
 The following best practices establish a verification mechanism to assure that
 the issuer is the owner of the key used in a credential.
@@ -556,7 +556,7 @@ Prior designed cryptosuites in both OB 3.0 and CLR 2.0 were:
 #### Key provenance
 
 Keys used in proof generation must belong to the issuer. However, there isn't
-a existing way in current standars to completely assure this provenance.
+a existing way in current standards to completely assure this provenance.
 
 The following best practices establish a verification mechanism to assure that
 the issuer is the owner of the key used in a credential.