update docs

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

en/contribute/OpenHarmony-security-design-guide.md

@@ -154,7 +154,7 @@ RSA/DSA, with a key length less than 2048 bits
 
 - When calculating the one-way password hash using PBKDF2, the number of iterations is at least 1000. 
 - A salt value is a cryptographically secure random number generated by the system. The salt value has at least 16 bytes and is unique to each user. 
-- Avoid using HASH(user name\|\|password), HMAC(user name, password), and HASH(password XOR salt).
+- Avoid using HASH (user name\|\|password), HMAC (user name, password), and HASH (password XOR salt).
 
 4-3 If sensitive data needs to be transmitted over untrusted networks, ensure that sensitive data is transmitted over secure paths or is transmitted after being encrypted
 
@@ -213,7 +213,7 @@ TFTP, FTP, Telnet, SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, SNMPv1/v2, and SSHv1.x
 
 **Description**: Precise location information is very sensitive, and is not needed in troubleshooting.
 
-6-6 Collect personal data necessary for stated purposes in compliance with the data minimization principle. Comply with the data minimization principle when displaying personal data in fault diagnosis logs.
+6-6 Collect personal data necessary for stated purposes in compliance with the data minimization principle. Comply with the data minimization principle when displaying personal data in fault diagnosis logs
 
 **Description**: The display of personal data in fault diagnosis logs may arouse users' doubts. Therefore, personal data should not be displayed in fault diagnosis logs. If it has to be displayed (for example, for debugging purpose) anonymization is required.