Fix some type issues

sonic-net · Mar 9, 2022 · 3d4f19c · 3d4f19c
1 parent 30f4f2b
commit 3d4f19c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/doc/sonic-build-system/SONiC-OpenSSL-FIPS-140-3.md b/doc/sonic-build-system/SONiC-OpenSSL-FIPS-140-3.md
@@ -41,7 +41,7 @@ SONiC only uses cryptographic modules validated by FIPS 140-3, Make SONiC compli
 | -------------------- | --------------- | -------------------------------------------- |
 | OpenSSL              | Python, OpenSSH | Cyptography and SSL/TLS ToolKit              |
 | Kerberos             | OpenSSH         | Kerboros contains builtin crypto module      |
-| Golang               | sonic-restapi   | Golang contains builtin crypt module         |
+| Golang               | sonic-restapi   | Golang contains builtin crypto module         |
 | Libgcrypto           | GPG             | A general purpose cryptographic library originally based on code from GnuPG |
 | Kernel Crypto        | --              | Linux crypto kernel module |
 
@@ -63,7 +63,7 @@ Out of Scopes:
 OpenSSL supports engine cryptographic modules in the form of engine objects, and provides a reference-counted mechanism to allow them to be dynamically loaded in and out of the running application. An engine object can implement one or all cryptographic algorithms.
 
 ### SymCrypt OpenSSL Engine
-The [SymCrypt engine for OpenSSL (SCOSSL)](https://github.com/microsoft/SymCrypt-OpenSSL) allows the use of OpenSSL with [SymCrypt](https://github.com/microsoft/SymCrypt) as the provider for core cryptographic operations. It leverages the OpenSSL engine interface to override the cryptographic implementations in OpenSSL's libcrypto. The primary motivation for this is to support FIPS certification, as vanilla OpenSSL 1.1.1 does not have a FIPS-certified cryptographic module. Microsoft will submit the FIPS 140-3 reports for SymCrypt to CMVP.
+The [SymCrypt engine for OpenSSL (SCOSSL)](https://github.com/microsoft/SymCrypt-OpenSSL) allows the use of OpenSSL with [SymCrypt](https://github.com/microsoft/SymCrypt) as the provider for core cryptographic operations. It leverages the OpenSSL engine interface to override the cryptographic implementations in OpenSSL's libcrypto. The primary motivation for this is to support FIPS certification, as OpenSSL 1.1.1 does not have a FIPS-certified cryptographic module. Microsoft will submit the FIPS 140-3 reports for SymCrypt to CMVP.
 
 The SymCrypt Engine is one of the implementation to support FIPS, The [wolfSSL engine](https://github.com/wolfSSL/wolfEngine) is another option.