!13862 翻译完成 12668+13383+13602

Merge pull request !13862 from ester.zhou/TR-12668

!13862 翻译完成 12668+13383+13602
Merge pull request !13862 from ester.zhou/TR-12668
a21d0e6a · openharmony_ci · Gitee · 29f6ae7c · 02006029 · a21d0e6a
3 changed file
--- a/en/application-dev/quick-start/full-sdk-switch-guide.md
+++ b/en/application-dev/quick-start/full-sdk-switch-guide.md
@@ -4,7 +4,7 @@ Both the public SDK and full SDK are toolkits for application development. <br>T

 The full SDK is intended for original equipment manufacturers (OEMs) and provided separately. It contains system APIs.

-The SDK of API version 8 provided in DevEco Studio is a public SDK. If your project depends on any system API, such as the **animator** component, **XComponent**, or APIs in **@ohos.application.abilityManager.d.ts**, **@ohos.application.formInfo.d.ts**, or **@ohos.bluetooth.d.ts**, switch to the full SDK by performing the following steps.
+The SDK of API version 8 provided in DevEco Studio is a public SDK. If your project depends on any system API, such as the **animator** component, **xcomponent** component, or APIs in **@ohos.app.ability.abilityManager.d.ts**, **@ohos.app.form.formInfo.d.ts**, or **@ohos.bluetooth.d.ts**, switch to the full SDK by performing the following steps.

 > **NOTE**
 >
@@ -34,7 +34,7 @@ In DevEco Studio, choose **Tools** > **OpenHarmony SDK Manager** to check the lo

   ![image-20220613220702504](figures/en-us_image_0000001655129232.png)

-   b. Verify that the SDK contains system APIs (such as APIs defined in **@ohos.application.abilityManager.d.ts**, **@ohos.application.formInfo.d.ts**, and **@ohos.bluetooth.d.ts**).
+   b. Verify that the SDK contains system APIs, including the APIs in **@ohos.app.ability.abilityManager.d.ts**, **@ohos.app.form.formInfo.d.ts**, and **@ohos.bluetooth.d.ts**.

   Note: The criteria for identifying system APIs are subject to the official API documentation.


--- a/en/application-dev/ui/arkui-overview.md
+++ b/en/application-dev/ui/arkui-overview.md
@@ -37,7 +37,7 @@ As shown above, the two development paradigms share the UI backend engine and la

 ## Relationship Between UI and Ability Framework

-OpenHarmony provides two application models: FA model and stage model. The table below describes the relationship between these two models and the two development paradigms of ArkUI.
+OpenHarmony provides two [application models](../application-models/application-model-description.md): FA model and stage model. The table below describes the relationship between these two models and the two development paradigms of ArkUI.

 **FA Model**

@@ -46,13 +46,13 @@ OpenHarmony provides two application models: FA model and stage model. The table
 | Application  | Web-like development paradigm| UI development: HML, CSS, and JS<br>Service entries: files with fixed file names, which are **app.ets** (Page ability), **service.ts** (Service ability), and **data.ts** (Data ability)<br>Service logic: JS and TS|
 |      | Declarative development paradigm | UI development: ArkTS<br>Service entries: files with fixed file names, which are **app.ets** (Page ability), **service.ts** (Service ability), and **data.ts** (Data ability)<br>Service logic: JS and TS|
 | Service widget| Web-like development paradigm| UI development: HML, CSS, and JSON (action)<br>Service entry: **form.ts**<br>Service logic: JS and TS|
-|      | Declarative development paradigm | Not supported currently                                   |
+|      | Declarative development paradigm | Not supported                                   |

 **Stage Model**

-| Type  | UI Development Paradigm  | Description                                      |
-| ---- | -------- | ---------------------------------------- |
-| Application  | Web-like development paradigm| Not supported currently                                   |
-|      | Declarative development paradigm | UI development: ArkTS<br>Service entries: derived from **ohos.application.Ability**/**ExtensionAbility**<br>Service logic: TS|
-| Service widget| Web-like development paradigm| UI development: HML, CSS, and JSON (action)<br>Service entries: derived from **FormExtensionAbility**<br>Service logic: TS|
-|      | Declarative development paradigm | Not supported currently                                   |
+| Type    | UI Development Paradigm    | Description                                                        |
+| -------- | -------------- | ------------------------------------------------------------ |
+| Application    | Web-like development paradigm | Not supported                                                  |
+|          | Declarative development paradigm| UI development: ArkTS<br>Service entries: derived from **ohos.app.ability.UIAbility**/**ExtensionAbility**<br>Service logic: TS|
+| Service widget| Web-like development paradigm | UI development: HML, CSS, and JSON (action)<br>Service entries: derived from **FormExtensionAbility**<br>Service logic: TS|
+|          | Declarative development paradigm| Not supported                                                  |
--- a/en/application-dev/ui/ui-ts-components-web.md
+++ b/en/application-dev/ui/ui-ts-components-web.md
@@ -4,7 +4,7 @@ The **\<Web>** component can be used to display web pages. For details, see [Web

 ## Creating a Component

-Create a **\<Web>** component in the .ets file under **main/ets/MainAbility/pages**. Then, in the created component, use **src** to specify the web page URI to be referenced, and bind a controller to the component to call the component APIs.
+Create a **\<Web>** component in the .ets file under **main/ets/entryability/pages**. Then, in the created component, use **src** to specify the web page URI to be referenced, and bind a controller to the component to call the component APIs.

  ```ts
  // xxx.ets