Merge branch '2022' of https://github.com/FuchsiaOS/FuchsiaOS-docs-zh_CN

 into 2022

get-started/_common/components/_product_session.md

@@ -4,12 +4,16 @@ Sessions are components that encapsulate a product’s user experience. The
 session framework serves as a boundary between the Fuchsia platform and the
 product-level user interaction. Each Fuchsia product defines a single session
 instance as the root of the product experience, which may or may not manage
-additional child components.
+additional child components. -->
+会话是一系列封装了产品用户体验的组件。会话框架充当 Fuchsia 平台和产品级用户之间交流的边界。每个 Fuchsia 产品都将单个会话实例定义为产品体验的根，它可能管理，也可能不管理其他子组件。
+
 
 The `session_manager` platform component starts the session component on boot
 and offers it a fixed set of capabilities necessary to support the session
 framework APIs for elements such as window management, input event handling, or
-accessibility.
+accessibility. -->
+`session_manager` 平台组件在启动时打开会话组件，并为其提供一组固定的功能，以支持诸如窗口管理、输入事件处理或无障碍功能等元素的会话框架 API。
 
-Note: For more details on the session framework, see
-[Introduction to the session framework](/concepts/session/introduction.md).
+<!-- Note: For more details on the session framework, see
+[Introduction to the session framework](/concepts/session/introduction.md). -->
+注: 要获取关于会话框架的更多细节，请参阅[会话框架介绍](/concepts/session/introduction.md)。

get-started/_common/fidl/_connecting_intro.md

@@ -1,3 +1,4 @@
+<!--
 A protocol handle is a well-known object that provides an implementation of a
 FIDL protocol that is discoverable using component namespaces. The component
 framework facilitates protocol discovery between
@@ -7,24 +8,47 @@ given client. Once the proper components are identified, the
 [Component Manager](/glossary/README.md#component-manager)
 initiates connections between components using handles found in each
 component's namespace.
+ -->
+协议句柄是一个很常见的对象，它提供了一个 FIDL 协议的实现，FIDL 协议可以通过组件命名空间找到。组件框架使用能力促进了[组件](/glossary/README.md#component)之间的协议发现。能力路由描述了哪个组件应该作为任何给定客户端的提供者。一旦确定了适当的组件，[组件管理器](/glossary/README.md#component-manager)就会使用每个组件命名空间中的句柄来启动组件之间的连接。
 
+<!--
 Consider the following example for a `fuchsia.example.Foo` protocol:
+ -->
+请参考以下 `fuchsia.example.Foo` 协议的示例：
 
+<!--
 ![Diagram showing how connecting components is a combination of capability
 routing and protocol serving. Components must serve the implementation of a
 protocol they offer to other components.]
 (/get-started/images/fidl/protocol-serving.png){: width="629"}
+ -->
+![图中显示了如何连接组件，组件是能力路由和协议服务的结合。组件必须为它们提供给其他组件的协议的实现来提供服务。](/get-started/images/fidl/protocol-serving.png){: width="629"}
 
+<!--
 The diagram highlights the main elements involved in performing the connection:
+ -->
+该图强调了执行连接所涉及的主要元素：
 
+<!--
 1.  The provider component statically **declares** the protocol in the
     `capabilities` section of the manifest. This enables the component framework
     to perform capability routing.
-1.  A client component statically **requests** the protocol in the `use` section
+ -->
+1.  提供者组件在清单的 `capabilities` 部分中静态地**声明**协议。这使组件框架能够执行能力路由。
+<!--
+2.  A client component statically **requests** the protocol in the `use` section
     of the manifest. This creates the `/svc/fuchsia.example.Foo` protocol entry
     in the client's namespace if capability routing is successful.
-1.  The provider code **publishes** the implementation at runtime. This creates
+ -->
+2.  客户端组件在清单（manifest）的 `use` 部分静态地**请求**协议。如果能力路由成功，这将在客户端的命名空间中创建 `/svc/fuchsia.example.Foo` 协议项。
+<!--
+3.  The provider code **publishes** the implementation at runtime. This creates
     a protocol entry at `/svc/fuchsia.example.Foo` in the provider's outgoing
     directory.
-1.  The client code **connects** to the protocol handle at runtime. This opens a
+ -->
+3.  提供者代码在运行时**发布**实现。这将在提供者传出目录中的 `/svc/fuchsia.example.Foo` 处创建一个协议项。
+<!--
+4.  The client code **connects** to the protocol handle at runtime. This opens a
     FIDL connection to the implementation running in the provider component.
+ -->
+4.  客户端代码在运行时**连接**到协议句柄。这将与运行在提供者组件中的实现打开一个 FIDL 连接。

get-started/_common/intro/_architecture.md

@@ -1,29 +1,54 @@
+<!-- 
 ![Data table showing high-level diagram of the entire Fuchsia system
 architecture, highlighting core components and subsystems.]
+(/get-started/images/intro/fuchsia-architecture.png){: width="1080"}
+ -->
+![展示整个 Fuchsia 系统架构的高层图表的数据表，强调了核心组件和子系统]
 (/get-started/images/intro/fuchsia-architecture.png){: width="1080"}
 
-The following architectural principles guide Fuchsia's design and development:
+<!-- The following architectural principles guide Fuchsia's design and development: -->
 
+以下架构性原则指导了 Fuchsia 的设计与开发：
+<!-- 
 * [**Simple:**][simple]
   Fuchsia makes it easy to create, maintain, and integrate software and hardware across a wide range of devices.
+ -->
 
+* [**简单：**][simple]Fuchsia 让创建、维护和集成软件与硬件在各种设备中都变得容易。
+<!-- 
 * [**Secure:**][secure]
   Fuchsia has a kernel and software model designed for modern computing.
+ -->
 
+* [**安全：**][secure]Fuchsia 有着为现代计算设计的内核和软件模型。
+<!-- 
 * [**Updatable:**][updatable]
   As a modular operating system, Fuchsia allows the kernel, drivers, and software components to be independently updatable.
+ -->
 
+* [**可升级：**][updatable]作为模块化操作系统，Fuchsia 允许内核、驱动和软件组件独立升级。
+<!-- 
 * [**Performant:**][performant]
   Fuchsia is designed for real world product requirements and optimized for performance.
+ -->
+* [**高性能：**][performant]Fuchsia 为真实世界产品需求设计，并为性能优化。
 
+<!-- 
 The core of the system is [Zircon][glossary.zircon], a kernel and collection of
 libraries for handling system startup and bootstrapping.
 All other system components are implemented in user space and isolated,
 reinforcing the **principle of least privilege**. This includes:
+ -->
 
+系统的核心是 [Zircon][glossary.zircon]，它是处理系统启动与引导的内核和一组库。其他所有系统组件都实现于用户空间并被隔离，再次强化了**最小特权原则**。这些组件包括：
+<!-- 
 *   Device drivers
 *   Filesystems
 *   Network stacks
+ -->
+*   设备驱动
+*   文件系统
+*   网络栈
 
 [glossary.zircon]: /glossary/README.md#zircon
 [simple]: /concepts/principles/simple.md

get-started/learn/intro/architecture.md

@@ -1,3 +1,4 @@
-# Fuchsia architecture
+<!-- # Fuchsia architecture -->
+# Fuchsia 架构
 
 <<../../_common/intro/_architecture.md>>