update docs

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

en/application-dev/file-management/app-sandbox-directory.md

@@ -73,7 +73,7 @@ The following figure shows the application file directories. The path of a file
    | distributedfiles | distributedFilesDir | Distributed file directory| Directory in **el2** for saving the application files that can be directly accessed across devices.<br>This directory is cleared when the application is uninstalled.| 
    | files | filesDir | Application file directory| Directory for saving the application's persistent files on the device.<br>This directory is cleared when the application is uninstalled.| 
    | cache | cacheDir | Application cache file directory| Directory for caching the downloaded files of the application or saving the cache files regenerated on the device.<br>This directory is automatically cleared when the size of the **cache** directory reaches the quota or the system storage space reaches a certain threshold. The user can also clear this directory by using a system space management application. <br>The application needs to check whether the file still exists and determine whether to cache the file again.| 
-   | preferences | preferencesDir | Preferences file directory| Directory for saving common application configuration and user preference data managed by using database APIs.<br>This directory is cleared when the application is uninstalled. For details, see [Data Persistence by User Preferences](../database/data-persistence-by-preferences.md).| 
+   | preferences | preferencesDir | Preferences file directory| Directory for saving common application configuration and user preference data managed by using database APIs.<br>This directory is cleared when the application is uninstalled. For details, see [Persisting Preferences Data](../database/data-persistence-by-preferences.md).| 
    | temp | tempDir | Temporary file directory| Directory for saving the files generated and required during the application's runtime on the device. <br>This directory is cleared when the application exits.| 
 
    The application file paths are used in the following scenarios:
@@ -92,5 +92,3 @@ The following figure shows the application file directories. The path of a file
       Used to store application preferences data, including preference files and configuration files. This directory applied to storing only a small amount of data.
    - Temporary file directory<br>
       Used to store temporarily generated data of an application, including cached database data and images, temporary log files, downloaded application installation package files. The data stored in this directory is deleted after being used.
-
-<!--no_check-->
\ No newline at end of file

en/application-dev/file-management/file-management-overview.md

@@ -23,6 +23,3 @@ The file systems can be classified into the following types based on the file st
 **Figure 1** Files in an OS
 
 ![File classification model](figures/file-classification-model.png)
-
-
-<!--no_check-->
\ No newline at end of file

en/application-dev/file-management/select-user-file.md

@@ -63,7 +63,11 @@ The **FilePicker** provides the following interfaces by file type:
    ```
 
 3. Create a **documentViewPicker** instance, and call [**select()**](../reference/apis/js-apis-file-picker.md#select-3) to open the **FilePicker** page for the user to select documents.
+
      After the documents are selected successfully, a result set containing the file URIs is returned. Further operations can be performed on the documents based on the file URIs.
+
+   For example, you can use [file management APIs](../reference/apis/js-apis-file-fs.md) to obtain file attribute information, such as the file size, access time, and last modification time, based on the URI. If you need to obtain the file name, use [startAbilityForResult](../../application-dev/application-models/uiability-intra-device-interaction.md).
+
    > **NOTE**
    >
    > Currently, **DocumentSelectOptions** is not configurable. By default, all types of user files are selected.
@@ -80,6 +84,32 @@ The **FilePicker** provides the following interfaces by file type:
      })
    ```
 
+   > **NOTE**
+   >
+   > Currently, **DocumentSelectOptions** does not provide the method for obtaining the file name. To obtain the file name, use **startAbilityForResult()**.
+
+   ```ts
+   let config = {
+     action: 'ohos.want.action.OPEN_FILE',
+     parameters: {
+       startMode: 'choose',
+     }
+   }
+   try {
+     let result = await context.startAbilityForResult(config, {windowMode: 1});
+     if (result.resultCode !== 0) {
+       console.error(`DocumentPicker.select failed, code is ${result.resultCode}, message is ${result.want.parameters.message}`);
+       return;
+     }
+     // Obtain the URI of the document.
+     let select_item_list = result.want.parameters.select_item_list;
+     // Obtain the name of the document.
+     let file_name_list = result.want.parameters.file_name_list;
+   } catch (err) {
+     console.error(`Invoke documentPicker.select failed, code is ${err.code}, message is ${err.message}`);
+   }
+   ```
+
 ## Selecting an Audio File
 
 1. Import the **FilePicker** module.

en/application-dev/file-management/set-security-label.md

 # Setting the Security Level of a Distributed File
 
-The security capabilities vary with devices. For example, small embedded devices provide fewer security capabilities than tablets. The security requirements also vary with data. For example, personal health information and bank card information are not expected to be accessed by devices of lower security levels. OpenHarmony provides a complete set of standards for data and device classification and custom data transfer policies for different devices. For details, see [Data and Device Security Classification](../database/access-control-by-device-and-data-level.md).
+The security capabilities vary with devices. For example, small embedded devices provide fewer security capabilities than tablets. The security requirements also vary with data. For example, personal health information and bank card information are not expected to be accessed by devices of lower security levels. OpenHarmony provides a complete set of standards for data and device classification and custom data transfer policies for different devices. For details, see [Data Security Labels and Device Security Levels](../database/access-control-by-device-and-data-level.md).
 
 ## Available APIs
 
@@ -39,4 +39,3 @@ securityLabel.setSecurityLabel(filePath, 's0').then(() => {
   console.error(`Failed to setSecurityLabel. Code: ${err.code}, message: ${err.message}`);
 });
 ```
-<!--no_check-->
\ No newline at end of file

en/application-dev/file-management/share-app-file.md

@@ -6,13 +6,13 @@ The file of an application can be shared with another application based on the f
 
 - You can also use **open()** of the ohos.file.fs module to share an application file with the specified permissions to another application based on the FD. After parsing the FD from **Want**, the target application can read and write the file by using **read()** and **write()** APIs of ohos.file.fs.
 
-You can use the related APIs to [share a file with another application](#sharing-a-file-with-another-application) or [use shared application files](#using-shared-files).
+You can use the related APIs to [share a file with another application](#sharing-a-file-with-another-application) or [use shared application files](#using-shared-application-files).
 
 ## File URI Specifications
 
 The file URIs are in the following format:
 
-  file://<bundleName>/<path>/\#networkid=<networkid>
+  file://<bundleName>/<path>
 
 - **file**: indicates a file URI.
 
@@ -20,8 +20,6 @@ The file URIs are in the following format:
 
 - *path*: specifies the application sandbox path of the file.
 
-- *networkid* (optional): specifies the device to which the file belongs in a distributed file system. Leave this parameter unspecified if the file location does not need to be set.
-
 ## Sharing a File with Another Application
 
 Before sharing application files, you need to [obtain the application file path](../application-models/application-context-stage.md#obtaining-the-application-development-path).