Update docs (17862)

Signed-off-by: Nester.zhou <ester.zhou@huawei.com>

en/application-dev/quick-start/in-app-hsp.md

 # In-Application HSP Development
 
 An in-application Harmony Shared Package (HSP) is a file used for code and resource sharing within an application (called the host application) and can only be invoked by a HAP or HSP of the same application.
-The in-application HSP is released with the Application Package (App Pack) of the host application and has the same bundle name and lifecycle as the host application.
+The in-application HSP is released with the Application Package (App Pack) of the host application, shares a process with the host application, and has the same bundle name and lifecycle as the host application.
 
 ## Developing an In-Application HSP
 
@@ -151,3 +151,59 @@ struct Index {
   }
 }
 ```
+
+### Redirecting to a Page in Another Bundle
+
+If you want to add a button in the **entry** module to jump to the menu page (**library/src/main/ets/pages/menu.ets**) in the **library** module, you can write the following code in the **entry/src/main/ets/MainAbility/Index.ets** file of the **entry** module:
+```ts
+import router from '@ohos.router';
+
+@Entry
+@Component
+struct Index {
+    @State message: string = 'Hello World'
+
+    build() {
+    Row() {
+        Column() {
+        Text(this.message)
+            .fontSize(50)
+            .fontWeight(FontWeight.Bold)
+        // Add a button to respond to user clicks.
+        Button() {
+            Text('click to menu')
+            .fontSize(30)
+            .fontWeight(FontWeight.Bold)
+        }
+        .type(ButtonType.Capsule)
+        .margin({
+            top: 20
+        })
+        .backgroundColor('#0D9FFB')
+        .width('40%')
+        .height('5%')
+        // Bind click events.
+        .onClick(() => {
+            router.pushUrl({
+              url: '@bundle:com.example.hmservice/library/ets/pages/menu'
+            }).then(() => {
+              console.log("push page success");
+            }).catch(err => {
+              console.error(`pushUrl failed, code is ${err.code}, message is ${err.message}`);
+            })
+        })
+      .width('100%')
+    }
+    .height('100%')
+    }
+  }
+}
+```
+The input parameter **url** of the **router.pushUrl** API is as follows:
+```ets
+'@bundle:com.example.hmservice/library/ets/pages/menu'
+```
+The **url** content template is as follows:
+```ets
+'@bundle:bundle name/module name/path/page file name (without the extension .ets)'
+```

en/application-dev/quick-start/multi-hap-objective.md

@@ -6,5 +6,3 @@
 - Flexible deployment: You can flexibly combine HAP files for device-specific deployment. Assume that an application contains one entry-type HAP file (**entry.hap**) and two feature-type HAP files (**Feature1.hap** and **Feature2.hap**). The **Entry.hap** file can be deployed on device A and device B, the **Feature1.hap** file can be deployed only on device A, and the **Feature2.hap** can be deployed only on device B. This means that you can combine the **Entry.hap** and **Feature1.hap** files and deploy them on device A, and combine the **Entry.hap** and **Feature2.hap** files and deploy them on device B.
 
 - On-demand loading: You can load modules only when they are needed, reducing the package size. Specifically, you can configure some HAP files of your application to be loaded on demand. For example, if some features are not used during application startup, you can configure them to be loaded only when they are needed, rather than being loaded at startup. This can reduce the size of the application package to some extent.
-
-- Easier resource sharing: The resources (including public resource files and public pages) and shared objects (.so library files) required by multiple HAP files can be stored in an independent HAP file. In this way, other HAP files can obtain the resources and files by accessing the HAP, which also reduces the size of the application package to some extent.

en/application-dev/quick-start/quickfix-debug.md

@@ -46,7 +46,7 @@ The command contains the following options:
 
 With the preceding **patch.json**, .abc, and .so files, run the following command to generate an .hqf file using the **app_packing_tool.jar** tool in the **toolchains** folder in the local OpenHarmony SDK path:
 ```shell
-$ java -jar app_packing_tool.jar --mode hqf --json-path patch.json --lib-path libs --ets-patch patchs --out-path entry-default-unsigned.hqf --force true
+$ java -jar app_packing_tool.jar --mode hqf --json-path patch.json --lib-path libs --ets-path patchs --out-path entry-default-unsigned.hqf --force true
 ```
 
 The command contains the following options.

en/application-dev/quick-start/shared-guide.md

@@ -8,13 +8,11 @@ Both the HAR and HSP are used to share code and resources and can contain code,
 
 ![in-app-hsp-har](figures/in-app-hsp-har.png)
 
-The HSP is designed to solve the following issues with the HAR:
-- When multiple HAPs reference the same HAR, the size of the App Pack swells.
-- When multiple HAPs reference the same HAR, some state variables in the HAR cannot be shared.
+The HSP aims to resolve the App Pack bloat resulting from multiple HAP files referencing the same HAR.
 
 Restrictions on the HSP:
 - The HSP and its invoking modules must be in the stage model.
-- The HSP and its invoking modules must use the **esmodule **compilation mode.
+- The HSP and its invoking modules must use the **esmodule** compilation mode.
 - The HSP does not support the declaration of **abilities** and **extensionAbilities** in its configuration file.
 
 The HSP can be classified as [in-application HSP](in-app-hsp.md) or [inter-application HSP](cross-app-hsp.md), depending on the configuration files and usage methods.