docs(style): optimize symbols

docs-source/src/en/about/changelog.md

@@ -173,7 +173,7 @@ Time zone of version release date: **UTC+8**
 - Added `generic` function to reflect and call generics, you can use it in `Class` or `CurrentClass`
 - obsolete the `buildOfAny` method, now use the `buildOf` method directly (without generics) to use the constructor to create a new object and get the result `Any`
 - Fixed the issue of null pointer exception when using `hasExtends`
-- `CurrentClass` added non-`lambda` method of calling
+- `CurrentClass` added non-**lambda** method of calling
 - `CurrentClass` adds `name` and `simpleName` functions
 - Completely rewrite the core method of `ReflectionTool`, sorting and classifying different search conditions
 - Fixed the problem that `Member` obtained by directly calling `declared` in `ReflectionTool` throws an exception
@@ -302,7 +302,7 @@ Time zone of version release date: **UTC+8**
 - ~~`YukiHookXposedInitProxy`~~ renamed to `IYukiHookXposedInit`, the original interface name has been invalidated and will be deleted directly in subsequent versions
 - Added `initZygote` and Resources Hook functions to support Hook Layout
 - Added `onXposedEvent` method to listen to all events of native Xposed API
-- Perform `inline` processing on the `lambda` of the Hook function to avoid generating excessively broken anonymous classes and improve the running performance after compilation
+- Perform `inline` processing on the **lambda** of the Hook function to avoid generating excessively broken anonymous classes and improve the running performance after compilation
 - Fixed `PrefsData` compiled method body copy is too large
 - Added `XSharePreference` readability test, which will automatically print a warning log if it fails
 - `PackageParam` adds `appResources`, `moduleAppResources`, `moduleAppFilePath` functions
@@ -330,7 +330,7 @@ Time zone of version release date: **UTC+8**
 - Fixed `YukiHookModulePrefs` working in `New XSharePreference` mode
 - Added `ModulePreferenceFragment`, now you can completely replace `PreferenceFragmentCompat` and start using the new functionality
 - Adapt the Sp data storage solution of `PreferenceFragmentCompat`, thanks to [mahoshojoHCG](https://github.com/mahoshojoHCG) for feedback
-- Update autohandlers and `Kotlin` dependencies to the latest version
+- Update autohandlers and Kotlin dependencies to the latest version
 - Fixed some bugs in documentation and code comments
 
 ### 1.0.77 | 2022.04.15 &ensp;<Badge type="danger" text="outdate" vertical="middle" />
@@ -421,7 +421,7 @@ Time zone of version release date: **UTC+8**
 - Added `MethodFinder` and `FieldFinder` new return value calling methods
 - Fixed possible problems and fix possible problems during the use of Tai Chi
 - Fixed possible problems with auto-generated Xposed entry classes
-- Added `android` type and `java` type in `type`
+- Added `android` type and Java type in `type`
 
 ### 1.0.6 | 2022.03.20 &ensp;<Badge type="danger" text="outdate" vertical="middle" />
 
@@ -438,7 +438,7 @@ Time zone of version release date: **UTC+8**
 
 - Fixed an annotation error
 - Temporarily fix a bug
-- Added a large number of `android` types in `type` and a small number of `java` types
+- Added a large number of `android` types in `type` and a small number of Java types
 - Fixed compatibility issues between new and old Kotlin APIs
 
 ### 1.0.5 | 2022.03.18 &ensp;<Badge type="danger" text="outdate" vertical="middle" />
@@ -474,7 +474,7 @@ Time zone of version release date: **UTC+8**
 
 - `RemedyPlan` adds `onFind` function
 - Integrate and modify some reflection API code
-- Added `java` type in `type`
+- Added Java type in `type`
 - Fixed the issue that ignored errors still output in the console
 
 ### 1.0 | 2022.02.14 &ensp;<Badge type="danger" text="outdate" vertical="middle" />

docs-source/src/en/about/future.md

@@ -46,4 +46,4 @@ We have provided the Xposed native API listening interface, you can find or view
 
 As an API, currently only docking `XposedBridge` as a compatibility layer still has certain limitations.
 
-Most `inline hook` do not have a `Java` compatibility layer, and the `Java` compatibility layer adaptation of `native hook` may be considered later.
+Most `inline hook` do not have a Java compatibility layer, and the Java compatibility layer adaptation of `native hook` may be considered later.

docs-source/src/en/api/public/com/highcapable/yukihookapi/YukiHookAPI.md

@@ -538,7 +538,7 @@ inline fun configs(initiate: Configs.() -> Unit)
 
 **Function Illustrate**
 
-> 对 `Configs` 类实现了一个 `lambda` 方法体。
+> 对 `Configs` 类实现了一个 **lambda** 方法体。
 
 你可以轻松地调用它进行配置。
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/core/YukiMemberHookCreator.md

@@ -736,7 +736,7 @@ inline fun result(initiate: Result.() -> Unit): Result
 
 **Function Example**
 
-你可以使用此方法为 `Result` 类创建 `lambda` 方法体。
+你可以使用此方法为 `Result` 类创建 **lambda** 方法体。
 
 > The following example
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/core/finder/members/ConstructorFinder.md

@@ -350,7 +350,7 @@ inline fun result(initiate: Process.() -> Unit): Process
 
 **Function Example**
 
-你可以使用 `lambda` 形式创建 `Result` 类。
+你可以使用 **lambda** 形式创建 `Result` 类。
 
 > The following example
 
@@ -467,7 +467,7 @@ inline fun result(initiate: Result.() -> Unit): Result
 
 **Function Example**
 
-你可以使用 `lambda` 形式创建 `Result` 类。
+你可以使用 **lambda** 形式创建 `Result` 类。
 
 > The following example
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/core/finder/members/FieldFinder.md

@@ -352,7 +352,7 @@ inline fun result(initiate: Result.() -> Unit): Result
 
 **Function Example**
 
-你可以使用 `lambda` 形式创建 `Result` 类。
+你可以使用 **lambda** 形式创建 `Result` 类。
 
 > The following example
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/core/finder/members/MethodFinder.md

@@ -494,7 +494,7 @@ inline fun result(initiate: Process.() -> Unit): Process
 
 **Function Example**
 
-你可以使用 `lambda` 形式创建 `Result` 类。
+你可以使用 **lambda** 形式创建 `Result` 类。
 
 > The following example
 
@@ -611,7 +611,7 @@ inline fun result(initiate: Result.() -> Unit): Result
 
 **Function Example**
 
-你可以使用 `lambda` 形式创建 `Result` 类。
+你可以使用 **lambda** 形式创建 `Result` 类。
 
 > The following example
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/factory/ReflectionFactory.md

@@ -536,7 +536,7 @@ inline fun <reified T> classOf(loader: ClassLoader?, initialize: Boolean): Class
 
 **Function Example**
 
-我们要获取一个 `Class` 在 `Kotlin` 下不通过反射时应该这样做。
+我们要获取一个 `Class` 在 Kotlin 下不通过反射时应该这样做。
 
 > The following example
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/factory/YukiHookFactory.md

@@ -22,7 +22,7 @@ You can use the **Chrome Translation Plugin** to translate entire pages for refe
 
 **Function Illustrate**
 
-> 这是 `YukiHookAPI` 相关 `lambda` 方法的封装类以及部分 API 用法。
+> 这是 `YukiHookAPI` 相关 **lambda** 方法的封装类以及部分 API 用法。
 
 ## IYukiHookXposedInit.configs <span class="symbol">- ext-method</span>
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/param/PackageParam.md

@@ -412,7 +412,7 @@ fun loadApp(isExcludeSelf: Boolean, vararg hooker: YukiBaseHooker)
 
 > 装载并 Hook 指定、全部包名的 APP。
 
-`name` 为 APP 的包名，后方的两个参数一个可作为 `lambda` 方法体使用，一个可以直接装载子 Hooker。
+`name` 为 APP 的包名，后方的两个参数一个可作为 **lambda** 方法体使用，一个可以直接装载子 Hooker。
 
 装载并 Hook 指定、全部包名的 APP。
 
@@ -422,7 +422,7 @@ fun loadApp(isExcludeSelf: Boolean, vararg hooker: YukiBaseHooker)
 
 **Function Example**
 
-你可以使用 `loadApp` 的 `lambda` 方法体形式或直接装载一个 Hooker。
+你可以使用 `loadApp` 的 **lambda** 方法体形式或直接装载一个 Hooker。
 
 > The following example
 
@@ -507,7 +507,7 @@ fun loadZygote(vararg hooker: YukiBaseHooker)
 
 > 装载 APP Zygote 事件。
 
-方法中的两个参数一个可作为 `lambda` 方法体使用，一个可以直接装载子 Hooker。
+方法中的两个参数一个可作为 **lambda** 方法体使用，一个可以直接装载子 Hooker。
 
 ## loadSystem <span class="symbol">- method</span>
 
@@ -535,7 +535,7 @@ fun loadSystem(vararg hooker: YukiBaseHooker)
 
 > 装载并 Hook 系统框架。
 
-方法中的两个参数一个可作为 `lambda` 方法体使用，一个可以直接装载子 Hooker。
+方法中的两个参数一个可作为 **lambda** 方法体使用，一个可以直接装载子 Hooker。
 
 ## withProcess <span class="symbol">- method</span>
 
@@ -567,7 +567,7 @@ fun withProcess(name: String, vararg hooker: YukiBaseHooker)
 
 > 装载并 Hook APP 的指定进程。
 
-`name` 为 APP 的进程名称，后方的两个参数一个可作为 `lambda` 方法体使用，一个可以直接装载子 Hooker。
+`name` 为 APP 的进程名称，后方的两个参数一个可作为 **lambda** 方法体使用，一个可以直接装载子 Hooker。
 
 ## loadHooker <span class="symbol">- method</span>
 

docs-source/src/en/api/public/com/highcapable/yukihookapi/hook/type/java/VariableTypeFactory.md

@@ -18,6 +18,6 @@ You can use the **Chrome Translation Plugin** to translate entire pages for refe
 
 **Function Illustrate**
 
-> 这是一个预置反射类型的常量类，主要为 `Java` 相关基本变量类型的 `Class` 内容，跟随版本更新会逐一进行增加。
+> 这是一个预置反射类型的常量类，主要为 Java 相关基本变量类型的 `Class` 内容，跟随版本更新会逐一进行增加。
 
 详情可 [点击这里](https://github.com/fankes/YukiHookAPI/blob/master/yukihookapi-core/src/main/java/com/highcapable/yukihookapi/hook/type/java/VariableTypeFactory.kt) 进行查看。

docs-source/src/en/api/special-features/reflection.md

@@ -1865,7 +1865,7 @@ field {
 }
 ```
 
-Expressing the type of `Boolean::class.javaPrimitiveType` in `Kotlin` is very long and inconvenient.
+Expressing the type of `Boolean::class.javaPrimitiveType` in Kotlin is very long and inconvenient.
 
 Therefore, `YukiHookAPI` encapsulates common type calls for developers, including Android related types and Java common types and **primitive type keywords**.
 

docs-source/src/en/config/api-example.md

@@ -12,7 +12,7 @@
 fun configs(initiate: Configs.() -> Unit)
 ```
 
-The `configs` method implements a `lambda` method body on the `Configs` class, which you can easily call for configuration.
+The `configs` method implements a **lambda** method body on the `Configs` class, which you can easily call for configuration.
 
 ::: tip
 

docs-source/src/en/guide/example.md

@@ -608,7 +608,7 @@ For more functions, please refer to [PackageParam.withProcess](../api/public/com
 
 ## Writing Optimization
 
-To make the code more concise, you can omit the name of `YukiHookAPI` and write your `onHook` entry as `lambda`.
+To make the code more concise, you can omit the name of `YukiHookAPI` and write your `onHook` entry as **lambda**.
 
 > The following example
 

docs-source/src/en/guide/home.md

@@ -4,7 +4,7 @@
 
 ## Background
 
-This is an efficient Hook API rebuilt based on the Xposed API using `Kotlin`, and creates rich function extensions for the development of Xposed Modules.
+This is an efficient Hook API rebuilt based on the Xposed API using Kotlin, and creates rich function extensions for the development of Xposed Modules.
 
 The name is taken from ["ももくり" heroine Yuki Kurihara](https://www.bilibili.com/bangumi/play/ss5016).
 
@@ -12,15 +12,15 @@ Formerly the Innocent Xposed API used in [Development Learning Project](https://
 
 ## Usage
 
-`YukiHookAPI` is built entirely with `Kotlin` `lambda` syntax.
+`YukiHookAPI` is built entirely with Kotlin **lambda** syntax.
 
 Abandoning the original less friendly `XposedHelpers`, you can use it to easily create Xposed Modules and easily implement custom Hook API.
 
 ## Language Requirement
 
-Please use `Kotlin`, the framework part of the code composition is also compatible with `Java` but the implementation of the basic Hook scene **may not work at all**.
+Please use Kotlin, the framework part of the code composition is also compatible with Java but the implementation of the basic Hook scene **may not work at all**.
 
-All demo code in this document will be described using `Kotlin`, if you don't know how to use `Kotlin` then you may not be able to use `YukiHookAPI`.
+All demo code in this document will be described using Kotlin, if you don't know how to use Kotlin then you may not be able to use `YukiHookAPI`.
 
 Part of the Java Demo code can be found [here](https://github.com/fankes/YukiHookAPI/tree/master/samples/demo-module/src/main/java/com/highcapable/yukihookapi/demo_module/hook/java), but not recommended.
 
@@ -30,7 +30,7 @@ Previously, when we built an Xposed Module, we first needed to create an `xposed
 
 Then, manually fill in your own entry class name into the file and use `XposedHelpers` to implement our Hook logic.
 
-Since `Kotlin` is the main Android development language, this API is really not very elegant to use.
+Since Kotlin is the main Android development language, this API is really not very elegant to use.
 
 Is there any **easy to use, light, elegant** solution?
 
@@ -38,7 +38,7 @@ With this idea, `YukiHookAPI` was born.
 
 Now, we only need to write a small amount of code, and all the time and expense are handed over to automation.
 
-With `Kotlin`'s elegant `lambda` writing and `YukiHookAPI`, you can make your Hook logic more beautiful and clear.
+With Kotlin's elegant **lambda** writing and `YukiHookAPI`, you can make your Hook logic more beautiful and clear.
 
 > The following example
 

docs-source/src/en/guide/knowledge.md

@@ -66,7 +66,7 @@ The Root-free frameworks mentioned above are [LSPatch](https://github.com/LSPose
 
 ### What YukiHookAPI does
 
-Since Xposed appeared until now, apart from `XposedHelpers`, which is well known to developers, there is still no set of syntactic sugar for `Kotlin` and API with complete usage encapsulation.
+Since Xposed appeared until now, apart from `XposedHelpers`, which is well known to developers, there is still no set of syntactic sugar for Kotlin and API with complete usage encapsulation.
 
 The birth of this API framework is to hope that in the current era of Xposed, more capable Xposed Module developers can avoid detours and complete the entire development process more easily and simply.
 

docs-source/src/en/guide/move-to-new-api.md

@@ -10,7 +10,7 @@ This document can help you quickly migrate from the Hook APIs you are familiar w
 
 > Migrated from `XC_LoadPackage.LoadPackageParam` to `PackageParam`.
 
-`YukiHookAPI` implements the `lambda` method body `this` usage for `PackageParam`, and the `PackageParam` object can be obtained globally in the `encase` method body.
+`YukiHookAPI` implements the **lambda** method body `this` usage for `PackageParam`, and the `PackageParam` object can be obtained globally in the `encase` method body.
 
 > The API function differences are compared as follows
 
@@ -107,7 +107,7 @@ override fun handleInitPackageResources(resparam: XC_InitPackageResources.InitPa
 
 #### Before/After Hook
 
-`YukiHookAPI` also implements the `lambda` method body `this` usage for `HookParam`, and the `HookParam` object can be obtained globally in the method bodies such as `beforeHook` and `afterHook`.
+`YukiHookAPI` also implements the **lambda** method body `this` usage for `HookParam`, and the `HookParam` object can be obtained globally in the method bodies such as `beforeHook` and `afterHook`.
 
 > The API function differences are compared as follows
 

docs-source/src/en/guide/quick-start.md

@@ -30,7 +30,7 @@ If you don't want to use automated build tools, you can still manually configure
 
 ### Create Project
 
-Use `Android Studio` or `IntelliJ IDEA` to create a new Android project and select `Kotlin` in the `Language` column to automatically add basic dependencies.
+Use `Android Studio` or `IntelliJ IDEA` to create a new Android project and select Kotlin in the `Language` column to automatically add basic dependencies.
 
 ### Integration Dependencies