!3031 #I4ZQHT 完成

Merge pull request !3031 from Annie_wang/PR2606

en/application-dev/database/database-relational-overview.md

-# RDB Overview<a name="EN-US_TOPIC_0000001231030607"></a>
+# RDB Overview
 
-The relational database \(RDB\) manages data based on relational models. With the underlying SQLite database, the RDB provides a complete mechanism for managing local databases. To satisfy different needs in complicated scenarios, the RDB offers a series of methods for performing operations such as adding, deleting, modifying, and querying data, and supports direct execution of SQL statements.
+The relational database (RDB) manages data based on relational models. With the underlying SQLite database, the RDB provides a complete mechanism for managing local databases. To satisfy different needs in complicated scenarios, the RDB offers a series of methods for performing operations such as adding, deleting, modifying, and querying data, and supports direct execution of SQL statements.
 
-## Basic Concepts<a name="section1063573420813"></a>
+## Basic concepts
 
--   **RDB**
+- **RDB**
 
-    A type of database based on the relational model of data. The RDB stores data in rows and columns. An RDB is also called RDB store.
+  A type of database created on the basis of relational models. The RDB stores data in rows and columns. A RDB is also called RDB store.
 
--   **Predicate**
+- **Predicate**
 
-    A representation of the property or feature of a data entity, or the relationship between data entities. It is mainly used to define operation conditions.
+  A representation of the property or feature of a data entity, or the relationship between data entities. It is mainly used to define operation conditions.
 
--   **Result set**
+- **Result set**
 
-    A set of query results used to access the data. You can access the required data in a result set in flexible modes.
+  A set of query results used to access data. You can access the required data in a result set in flexible modes.
 
--   **SQLite database**
+- **SQLite database**
 
-    A lightweight open-source relational database management system that complies with Atomicity, Consistency, Isolation, and Durability \(ACID\).
+  A lightweight open-source relational database management system that complies with Atomicity, Consistency, Isolation, and Durability (ACID).
 
+## Working Principles
 
-## Working Principles<a name="section4810552814"></a>
+The RDB provides common operation APIs for external systems. It uses the SQLite as the underlying persistent storage engine, which supports all SQLite database features.
 
-The RDB provides a common operation interface for external systems. It uses the SQLite as the underlying persistent storage engine, which supports all SQLite database features.
+**Figure 1** How RDB works
 
-**Figure  1**  How RDB works<a name="fig1826214361535"></a>  
-![](figures/how-rdb-works.png "how-rdb-works")
+![how-rdb-works](figures/how-rdb-works.png)
 
-## Default Settings<a name="section176091243121218"></a>
+## Default Settings
 
--   The default database logging mode is write-ahead logging \(WAL\).
--   The default database flush mode is Full mode.
--   The default shared memory used by the OpenHarmony database is 2 MB.
+- The default RDB logging mode is Write Ahead Log (WAL).
+- The default data flushing mode is **FULL** mode.
+- The default size of the shared memory used by an OpenHarmony database is 2 MB.
 
-## Constraints<a name="section929813398308"></a>
+## Constraints
 
--   A maximum of four connection pools can be connected to an RDB to manage read and write operations.
-
--   To ensure data accuracy, the RDB supports only one write operation at a time.
+- A maximum of four connection pools can be connected to an RDB to manage read and write operations.
 
+- To ensure data accuracy, the RDB supports only one write operation at a time.

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

@@ -128,7 +128,7 @@ Permissions can be classified into the following types based on the authorizatio
 
     This type of permissions must be declared in the app installation package and authorized by users dynamically during the running of the app. The app has the permission only after user authorization.
 
-    For example, in the [Permission List] (#permissionlist), the permissions for the microphone and camera are user_grant and need user authorization.
+    For example, in the [Permission List](#permissionlist), the permissions for the microphone and camera are user_grant permissions. The list provides reasons for using the permissions.
 
     The user_grant permission list must also be presented on the details page of the app store.