!16169 翻译完成：15769+16133 废弃接口修改+修改链接问题

Merge pull request !16169 from wusongqing/TR15769

en/application-dev/reference/apis/js-apis-bundle-BundleInstaller.md

@@ -160,9 +160,9 @@ bundle.getBundleInstaller().then(installer => {
 
 Describes the parameters required for bundle installation, recovery, or uninstall.
 
- **System capability**: SystemCapability.BundleManager.BundleFramework
+**System capability**: SystemCapability.BundleManager.BundleFramework
 
- **System API**: This is a system API and cannot be called by third-party applications.
+**System API**: This is a system API and cannot be called by third-party applications.
 
 | Name       | Type   | Readable| Writable| Description              |
 | ----------- | ------- | ---- | ---- | ------------------ |
@@ -174,17 +174,17 @@ Describes the parameters required for bundle installation, recovery, or uninstal
 
 Describes the bundle installation or uninstall status.
 
- **System capability**: SystemCapability.BundleManager.BundleFramework
+**System capability**: SystemCapability.BundleManager.BundleFramework
 
- **System API**: This is a system API and cannot be called by third-party applications.
+**System API**: This is a system API and cannot be called by third-party applications.
 
 | Name         | Type                                                        | Readable| Writable| Description                          |
 | ------------- | ------------------------------------------------------------ | ---- | ---- | ------------------------------ |
-| status        | bundle.[InstallErrorCode](js-apis-Bundle.md#installerrorcode) | Yes  | No  | Installation or uninstall error code. The value must be defined in [InstallErrorCode](js-apis-Bundle.md#installerrorcode). |
+| status        | bundle.[InstallErrorCode](js-apis-Bundle.md#installerrorcode) | Yes  | No  | Installation or uninstall error code. The value must be defined in [InstallErrorCode](js-apis-Bundle.md#installerrorcode)|
 | statusMessage | string                                                       | Yes  | No  | Installation or uninstall status message.  <br>**SUCCESS**: install_succeed<br>**STATUS_INSTALL_FAILURE**: Installation failed (no installation file exists).<br>**STATUS_INSTALL_FAILURE_ABORTED**: Installation aborted.<br>**STATUS_INSTALL_FAILURE_INVALID**: Invalid installation parameter.<br>**STATUS_INSTALL_FAILURE_CONFLICT**: Installation conflict. (The basic information of the application to update is inconsistent with that of the existing application.)<br>**STATUS_INSTALL_FAILURE_STORAGE**: Failed to store the bundle information.<br>**STATUS_INSTALL_FAILURE_INCOMPATIBLE**: Installation incompatibility. (A downgrade occurs or the signature information is incorrect.)<br>**STATUS_UNINSTALL_FAILURE**: Uninstallation failed. (The application to be uninstalled is not found.)<br>**STATUS_UNINSTALL_FAILURE_ABORTED**: Uninstallation aborted. (This error code is not in use.)<br>**STATUS_UNINSTALL_FAILURE_ABORTED**: Uninstallation conflict. (Failed to uninstall a system application or end the application process.)<br>**STATUS_INSTALL_FAILURE_DOWNLOAD_TIMEOUT**: Installation failed. (Download timed out.)<br>**STATUS_INSTALL_FAILURE_DOWNLOAD_FAILED**: Installation failed. (Download failed.)<br>**STATUS_RECOVER_FAILURE_INVALID**: Failed to restore the pre-installed application.<br>**STATUS_ABILITY_NOT_FOUND**: Ability not found.<br>**STATUS_BMS_SERVICE_ERROR**: BMS service error.<br>**STATUS_FAILED_NO_SPACE_LEFT**: Insufficient device space.<br>**STATUS_GRANT_REQUEST_PERMISSIONS_FAILED**: Application authorization failed.<br>**STATUS_INSTALL_PERMISSION_DENIED**: No installation permission.<br>**STATUS_UNINSTALL_PERMISSION_DENIED**: No uninstallation permission. |
 
 ## Obtaining the Sandbox Path
-For the FA model, the sandbox path of a bundle can be obtained using the APIs in [Context](js-apis-inner-app-context.md). For the stage model, the sandbox path can be obtained using the attribute in [Context](js-apis-ability-context.md#abilitycontext). The following describes how to obtain the sandbox path.
+For the FA model, the sandbox path of a bundle can be obtained using the APIs in [Context](js-apis-inner-app-context.md). For the stage model, the sandbox path can be obtained using the attribute in [Context](js-apis-inner-application-uiAbilityContext.md#abilitycontext). The following describes how to obtain the sandbox path.
 
 **Example**
 ``` ts

en/application-dev/reference/apis/js-apis-system-vibrate.md

 # @system.vibrator (Vibrator)
 
-
 The **Vibrator** module provides APIs for controlling LED lights and vibrators. You can use the APIs to query the LED light list, turn on and off the LED light, query the vibrator list, query the vibrator effect, and trigger and turn off the vibrator.
 
 Misc devices refer to LED lights and vibrators on devices. LED lights are mainly used for indication (for example, indicating the charging state) and blinking (such as tri-colored lights). Vibrators are mainly used in scenarios such as the alarm clock, power-on/off, and incoming call vibration.
 
 
 > **NOTE**
-> - The initial APIs of this module are supported since API version 4. Newly added APIs will be marked with a superscript to indicate their earliest API version.
+> - The initial APIs of this module are supported since API version 3. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 > - The APIs of this module are no longer maintained since API version 8. You are advised to use [`@ohos.vibrator`](js-apis-vibrator.md) instead.
 > - This module requires hardware support and can only be debugged on real devices.
 
@@ -21,26 +20,23 @@ import vibrator from '@system.vibrator';
 
 ## vibrator.vibrate
 
-vibrate(Object): void
+ vibrate(options?: VibrateOptions): void
 
 Triggers device vibration.
 
-**System capability**: SystemCapability.Sensors.MiscDevice
+**Required permissions**: ohos.permission.VIBRATE
 
-**Required permissions**: ohos.permission.VIBRATE (a system permission)
+**System capability**: SystemCapability.Sensors.MiscDevice
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| -------- | -------- | -------- | -------- |
-| mode | string | No| Vibration mode. The value **long** indicates long vibration, and **short** indicates short vibration. The default value is **long**.|
-| success | Function | Yes| Called when the vibrator data changes.|
-| fail | Function | No| Called when the API call fails.|
-| complete | Function | No| Called when the API call is complete.|
+| Name | Type                             | Mandatory| Description      |
+| ------- | --------------------------------- | ---- | ---------- |
+| options | [VibrateOptions](#vibrateoptions) | No  | Vibration options.|
 
 **Example**
 
-```
+```js
 vibrator.vibrate({
   mode: 'short',
   success: function() {
@@ -54,3 +50,18 @@ vibrator.vibrate({
   }
 });
 ```
+
+## VibrateOptions
+
+Defines the vibration options.
+
+**Required permissions**: ohos.permission.VIBRATE
+
+**System capability**: SystemCapability.Sensors.MiscDevice
+
+| Name    | Type    | Mandatory| Description                                                        |
+| -------- | -------- | ---- | ------------------------------------------------------------ |
+| mode     | string   | No  | Vibration mode. The value **long** indicates long vibration, and **short** indicates short vibration. The default value is **long**.|
+| success  | Function | No  | Called when the vibrator data changes.                            |
+| fail     | Function | No  | Called when the API call fails.                                    |
+| complete | Function | No  | Called when the API call is complete.                                    |