fix title

docs/api/description/builtin-policies.md

@@ -1,4 +1,4 @@
-# Build policies
+# Build Policies
 
 Xmake has many default behaviors, such as: automatic detection and mapping of flags, cross-target parallel construction, etc. Although it provides a certain amount of intelligent processing, it is difficult to adjust and may not meet all users' habits and needs.
 

docs/api/description/builtin-rules.md

@@ -1,5 +1,5 @@
 
-# Builtin rules
+# Builtin Rules
 
 sinceAfter the 2.2.1 release, xmake provides some built-in rules to simplify the daily xmake.lua description and support for some common build environments.
 

docs/api/description/builtin-variables.md

@@ -1,4 +1,4 @@
-# Builtin variables
+# Builtin Variables
 
 Xmake provides the syntax of `$(varname)` to support the acquisition of built-in variables, for example:
 

docs/api/description/configuration-option.md

@@ -1,4 +1,4 @@
-# Configuration option
+# Configuration Option
 
 Define and set option switches. Each `option` corresponds to an option that can be used to customize the build configuration options and switch settings.
 

docs/api/description/custom-rule.md

@@ -1,4 +1,4 @@
-# Custom rule
+# Custom Rule
 
 After the 2.2.1 release, xmake not only natively supports the construction of multi-language files, but also allows users to implement complex unknown file builds by custom building rules.
 

docs/api/description/custom-toolchain.md

@@ -1,4 +1,4 @@
-# Custom toolchain
+# Custom Toolchain
 
 After version 2.3.4, xmake has supported custom toolchain in user's project xmake.lua, for example:
 

docs/api/description/global-interfaces.md

@@ -1,4 +1,4 @@
-# Global interfaces
+# Global Interfaces
 
 The global interface affects the whole project description scope and all sub-project files.
 

docs/api/description/helper-interfaces.md

@@ -1,4 +1,4 @@
-# Helper interfaces
+# Helper Interfaces
 
 In addition, the version of this interface after 2.2.5 provides some built-in helper functions, which can be imported directly using includes. See the specific built-in functions: [Helper functions](https://github.com/xmake- io/xmake/tree/master/xmake/includes)
 

docs/api/description/package-dependencies.md

@@ -1,4 +1,4 @@
-# Package dependencies
+# Package Dependencies
 
 ## package
 

docs/api/description/project-target.md

@@ -1,4 +1,4 @@
-# Project target
+# Project Targets
 
 We can use `target("test")` to define a project target named "test", each target generates an executable program, a static library, or a dynamic library.
 

docs/api/description/xpack-component-interfaces.md

@@ -1,4 +1,4 @@
-# XPack Component interfaces
+# XPack Component Interfaces
 
 ## set_title
 

docs/api/description/xpack-interfaces.md

@@ -1,4 +1,4 @@
-# Packaging interface
+# XPack Interfaces
 
 Xpack is provided as a plug-in, and all its APIs need to be introduced through `includes("@builtin/xpack")`.
 

docs/api/scripts/native-modules.md

@@ -1,3 +1,4 @@
+# Native Modules
 
 We know that in xmake, you can import some lua modules through the import interface for use in the script domain. However, if the operation of some modules is time-consuming, then lua implementation is not an ideal choice.
 Therefore, in the new version, we have added support for the native lua module, which can be implemented through native to achieve speed-up optimization. Moreover, importing and using the module is as simple as the lua module.

docs/api/scripts/package-instance.md

@@ -1,4 +1,4 @@
-# Package instance
+# Package Instance
 
 This page describes the interface for `package` of functions like `on_load()`, `on_install()` or `on_test()` of the [Package Dependencies](/api/description/package-dependencies)
 

docs/api/scripts/target-instance.md

@@ -1,4 +1,4 @@
-# Target instance
+# Target Instance
 
 This page describes the interface for `target` of functions like `on_load()`, `before_build()` or `after_install()` of the [Project target](/api/description/project-target).
 

docs/guide/extras/environment-variables.md

@@ -1,4 +1,4 @@
-# Environment variables
+# Environment Variables
 
 We can execute the following command to get all the environment variables used by xmake and the currently set values.
 

docs/guide/package-management/using-local-packages.md

@@ -1,4 +1,4 @@
-# Using Local packages
+# Using Local Packages
 
 ## Generate a local package
 

docs/guide/project-configuration/namespace-isolation.md

@@ -1,4 +1,4 @@
-# Namespace isolation {#namespace-isolation}
+# Namespace Isolation {#namespace-isolation}
 
 If the user maintains two independent sub-projects, and there are some targets, options, and rule names with the same name, when they are integrated into one project through includes, there may be a naming conflict that causes compilation errors.
 

docs/zh/api/scripts/native-modules.md

@@ -1,3 +1,4 @@
+# 原生模块 {#native-modules}
 
 我们知道，在 xmake 中，可以通过 import 接口去导入一些 lua 模块在脚本域中使用，但是如果一些模块的操作比较耗时，那么 lua 实现并不是理想的选择。
 因此，新版本中，我们新增了 native lua 模块的支持，可以通过 native 实现，来达到提速优化的效果，并且模块导入和使用，还是跟 lua 模块一样简单。