update docs

Signed-off-by: NAnnie_wang <annie.wangli@huawei.com>

en/application-dev/security/cryptoFramework-guidelines.md

@@ -32,10 +32,10 @@ The table below describes the APIs used in this guide.
 |AsyKeyGenerator|generateKeyPair() : Promise\<KeyPair>|Generates an asymmetric key pair randomly. This API uses a promise to return the result.|
 |SymKeyGenerator|generateSymKey(callback : AsyncCallback\<SymKey>) : void|Generates a symmetric key randomly. This API uses an asynchronous callback to return the result.|
 |SymKeyGenerator|generateSymKey() : Promise\<SymKey>|Generates a symmetric key randomly. This API uses a promise to return the result.|
-| AsyKeyGenerator          | convertKey(pubKey : DataBlob, priKey : DataBlob, callback : AsyncCallback\<KeyPair>) : void | Converts binary data into a key pair. This API uses an asynchronous callback to return the result.<br>(**pubKey** or **priKey** can be **null**. That is, you can pass in only **pubKey** or **priKey**. As a result, the return **KeyPair** instance contains only the public or private key.)|
-| AsyKeyGenerator          | convertKey(pubKey : DataBlob, priKey : DataBlob) : Promise\<KeyPair> | Converts the binary data into a key pair. This API uses a promise to return the result.<br>(**pubKey** or **priKey** can be **null**. That is, you can pass in only **pubKey** or **priKey**. As a result, the returned **KeyPair** instance contains only the public or private key.)|
-| SymKeyGenerator         | convertKey(key : DataBlob, callback : AsyncCallback\<SymKey>) : void| Converts binary data into a symmetric key. This API uses an asynchronous callback to return the result.|
-| SymKeyGenerator         |convertKey(pubKey : DataBlob, priKey : DataBlob) : Promise\<KeyPair>| Converts binary data into a symmetric key. This API uses a promise to return the result.|
+| AsyKeyGenerator          | convertKey(pubKey : DataBlob, priKey : DataBlob, callback : AsyncCallback\<KeyPair>) : void | Converts the binary data into a key pair. This API uses an asynchronous callback to return the result.<br>(**pubKey** or **priKey** can be **null**. That is, you can pass in only **pubKey** or **priKey**. As a result, the return **KeyPair** instance contains only the public or private key.) |
+| AsyKeyGenerator          | convertKey(pubKey : DataBlob, priKey : DataBlob) : Promise\<KeyPair> | Converts the binary data into a key pair. This API uses a promise to return the result.<br>(**pubKey** or **priKey** can be **null**. That is, you can pass in only **pubKey** or **priKey**. As a result, the returned **KeyPair** instance contains only the public or private key.) |
+| SymKeyGenerator         | convertKey(key : DataBlob, callback : AsyncCallback\<SymKey>) : void| Converts the binary data into a symmetric key. This API uses an asynchronous callback to return the result. |
+| SymKeyGenerator         |convertKey(pubKey : DataBlob, priKey : DataBlob) : Promise\<KeyPair>| Converts the binary data into a symmetric key. This API uses a promise to return the result. |
 | Key | getEncoded() : DataBlob;  | Obtains the binary data of a key. (The child class instances of **Key** include **SymKey**, **PubKey**, and **PriKey**.)|
 
 **How to Develop**
@@ -121,11 +121,11 @@ function convertAsyKey() {
 }
 ```
 
-**NOTE**
-
-The public key returned by **convertKey()** must be in the DER format complying with X.509 specifications, and the private key must be in the DER format complying with PKCS #8 specifications.
+> **NOTE**
+>
+> The public key returned by **convertKey()** must be in the DER format complying with X.509 specifications, and the private key must be in the DER format complying with PKCS #8 specifications.
 
-Example 4: Generate an asymmetric key pair from the binary ECC key data.
+ Example 4: Generate an asymmetric key pair from the binary ECC key data.
 
 1. Obtain the ECC binary key data and encapsulate it into a **DataBlob** instance.
 2. Call **convertKey()** to convert the key binary data (data of the private or public key, or both) passed in to a **KeyPair** instance.
@@ -492,17 +492,9 @@ function test3DesEcb() {
 
 Example 2: Encrypt and decrypt data using an asymmetric key pair.
 
-1. Generate an RSA key pair. 
-
-   Call **createAsyKeyGenerator()** to create an **AsyKeyGenerator** instance and generate an RSA asymmetric key pair.
-
-2. Create a **Cipher** instance.
-
-   Call **createCipher()** to create a **Cipher** instance, and set the key and encryption/decryption mode.
-
-3. Perform encryption and decryption operations.
-
-   Call **doFinal()** provided by the **Cipher** instance to encrypt data or decrypt data.
+1. Generate an RSA key pair.<br> Call **createAsyKeyGenerator()** to create an **AsyKeyGenerator** instance and generate an RSA asymmetric key pair.
+2. Create a **Cipher** instance.<br> Call **createCipher()** to create a **Cipher** instance, and set the key and encryption/decryption mode.
+3. Perform encryption and decryption operations.<br> Call **doFinal()** provided by the **Cipher** instance to encrypt data or decrypt data.
 
 ```javascript
 import cryptoFramework from "@ohos.security.cryptoFramework"
@@ -548,19 +540,19 @@ function encryptMessageCallback() {
 }
 ```
 
-**NOTE**
-
-- In RSA encryption and decryption, **init()** cannot be repeatedly called to initialize the **Cipher** instance. You must create a **Cipher** instance for each of encryption and decryption.
-- The RSA encryption has a limit on the length of the plaintext to be encrypted. For details, see "Basic Concepts" in [Crypto Framework Overview](cryptoFramework-overview.md).
-- In RSA decryption, the length of the ciphertext to be decrypted each time is the number of bits of the RSA key divided by 8.
+> **NOTE**
+>
+> - In RSA encryption and decryption, **init()** cannot be repeatedly called to initialize the **Cipher** instance. You must create a **Cipher** instance for each of encryption and decryption.
+> - The RSA encryption has a limit on the length of the plaintext to be encrypted. For details, see "Basic Concepts" in [Crypto Framework Overview](cryptoFramework-overview.md).
+> - In RSA decryption, the length of the ciphertext to be decrypted each time is the number of bits of the RSA key divided by 8.
 
 ## Signing Data and Verifying Signatures
 
 **When to Use**
 
 A digital signature can be used to verify the authenticity of a message. Typical signing and signature verification operations involve the following:
-1. Use RSA to sign data and verify the signature.
-2. Use ECC to sign data and verify the signature.
+- Use RSA to sign data and verify the signature.
+- Use ECC to sign data and verify the signature.
 
 **Available APIs**
 
@@ -764,7 +756,7 @@ Typical message digest operations involve the following:
 
 1. Create an **Md** instance.
 2. Add one or more segments of data for generating a digest.
-3. Compute a digest.
+3. Compute a digest. 
 4. Obtain the algorithm and length of a digest.
 
 **Available APIs**
@@ -1058,8 +1050,8 @@ function doHmacByCallback(algName) {
 
 Typical random number operations involve the following:
 
-- Generate a random number.
-- Set a seed based on the random number generated.
+1. Generate a random number.
+2. Set a seed based on the random number generated.
 
 **Available APIs**
 

en/application-dev/security/huks-guidelines.md

@@ -2,7 +2,7 @@
 
 OpenHarmony Universal KeyStore (HUKS) provides KeyStore (KS) capabilities for applications, including key management and key cryptography operations. HUKS also provides APIs for applications to import or generate keys.
 
-> **NOTE**<br>
+> **NOTE**
 >
 > This document is based on API version 9 and applies only to ArkTS development.
 
@@ -20,9 +20,9 @@ Generate a key for an application by specifying the alias and key parameters.
 
 > **NOTE**
 >
-> 1. When a key is used if the parameters passed in does not comply with the parameters passed in during the key generation, the parameter verification will fail. 
+> - When a key is used if the parameters passed in does not comply with the parameters passed in during the key generation, the parameter verification will fail. 
 >
-> 2. If an optional parameter required by the algorithm is not passed in during the key generation process, it must be passed in when the key is used.
+> - If an optional parameter required by the algorithm is not passed in during the key generation process, it must be passed in when the key is used.
 
 **Supported Key Types**
 

en/application-dev/security/userauth-overview.md

@@ -16,7 +16,7 @@ Facial recognition establishes a secure channel between a camera and a trusted e
 
 Facial characteristics are stored in the TEE, which uses strong cryptographic algorithms to encrypt and protect the integrity of facial characteristics. The collected and stored facial characteristics will not be transferred out of the TEE without user authorization. This ensures that system or third-party applications cannot obtain facial characteristics, or send or back them up to any external storage medium.
 
-## Limitations and Constraints
+## Constraints
 
 -   OpenHarmony only supports facial recognition and local authentication, and does not support an authentication UI.
 -   To use biometric recognition, a device must have a camera with a face image pixel greater than 100x100.