docs: update

Author: ulivz

packages/docs/docs/miscellaneous/glossary.md

@@ -6,25 +6,27 @@ sidebar: auto
 
 You may encounter some unfamiliar concepts in the documentation. This section lists the common terms in the documentation for easy access, learning and plugin/theme development.
 
-## frontmatter
+## layout
 
-> Access: `$page.frontmatter`
+- Access: `$page.frontmatter.layout`
 
-Configuration wrapped by `---` in the `markdown` file of the current page, which is generally used to do some page-level configuration.
+Name of the layout component used by the current page.
 
-::: tip
-Features such as VuePress's dynamic layout system are based on `frontmatter`. You can use the plugin API [extendPageData](../plugin/option-api.md#extendpagedata) to dynamically modify the value of frontmatter during build time.
-:::
+## frontmatter
+
+- Access: `$page.frontmatter`
+
+Configuration wrapped by `---` in the `markdown` file of the current page, which is generally used to do some page-level configuration. For more details, please see [Front Matter](../guide/frontmatter.md).
 
 ## permalink
 
-> Access: `$page.frontmatter.permalink`
+- Access: `$page.frontmatter.permalink`
 
-For permalinks, see [permalinks](../guide/permalinks.md) for more.
+Permalinks. For more details, please head [permalinks](../guide/permalinks.md).
 
 ## regularPath
 
-> Access: `$page.regularPath`
+- Access: `$page.regularPath`
 
 The current page is based on the URL generated by the directory structure.
 
@@ -34,36 +36,43 @@ When dynamically generating routes during the build period, a page's URL (`$page
 
 ## headers
 
-> Access: `$page.headers`
+- Access: `$page.headers`
 
 That is, those titles defined by one or more `#` in `markdown`.
 
 ## siteConfig
 
-> Access: `$site | Context.siteConfig`
+- Access: `$site | Context.siteConfig`
 
 `.vuepress/config.js`, i.e., `site configuration`。
 
 ## themeConfig
 
-> Access: `$site | Context.themeConfig`
+- Access: `$site | Context.themeConfig`
 
 Value of `themeConfig` in `.vuepress/config.js`, i.e., `user's theme configuration`.
 
 ## themePath
 
-> Access: `Context.themeAPI.theme.path`
+- Access: `Context.themeAPI.theme.path`
 
 Root path (absolute path) of the currently used theme.
 
 ## themeEntry
 
-> Access: `Context.themeAPI.theme.entry`
+- Access: `Context.themeAPI.theme.entry`
 
-Theme's configuration file (`themePath/index.js`).
+Theme's configuration file - `themePath/index.js`.
 
-## layout
+## parentThemePath
 
-> Access: `$page.frontmatter.layout`
+- Access: `Context.themeAPI.parentTheme.path`
+
+If the current theme is a derived theme, `parentThemePath` refers to the absolute path of the parent theme.
+
+## parentThemeNetry
+
+- Access: `Context.themeAPI.parentTheme.entry`
+
+If the current theme is a derived theme, `parentThemePath` refers to the theme configuration of the parent theme.
 
-Name of the layout component used by the current page.

packages/docs/docs/theme/inheritance.md

@@ -4,7 +4,7 @@
 
 We have two main reasons to support this feature:
 
-1. VuePress provides users with a [default theme](./default-theme-config.md), which meets the needs of document writers in most scenarios, even so, there are still many users who choose to `eject` and modify, even if they may only need to make minor changes to one of the components.
+1. VuePress provides users with a [default theme](./default-theme-config.md), which meets the needs of document writers in most scenarios, even so, there are still many users who choose to `eject` and modify it, even if they may only need to make minor changes to one of the components.
 
 2. In [0.x](https://vuepress.vuejs.org/guide/custom-themes.html#site-and-page-metadata), only one `Layout.vue` is needed for a theme, so we can achieve simple expansion by directly wrapping `Layout.vue` of another theme.
 
@@ -17,15 +17,15 @@ Therefore, we need to provide a reasonable and reliable theme inheritance strate
 To introduce this section, let's start with a few basic concepts:
 
 - **Atomic theme**：i.e. the parent theme, which is implemented entirely from scratch, like the default theme.
-- **Derived theme**：i.e. the child theme, created based on parent theme;
+- **Derived theme**：i.e. the child theme, which is created based on parent theme.
 
 ::: tip
-For now theme inheritance doesn't support high-level inheritance, that means, a derived topic cannot be inherited.
+For now theme inheritance doesn't support high-order inheritance, that means, a derived theme cannot be inherited.
 :::
 
 ## Usage
 
-Suppose you want to create a theme inherited from the default theme of VuePress, you just need to configure the [extend](./option-api.md#extend) option in your theme configuration:
+Suppose you want to create a theme inherited from the default theme, you just need to configure the [extend](./option-api.md#extend) option in your theme configuration:
 
 ```js
 module.exports = {
@@ -35,9 +35,9 @@ module.exports = {
 
 ## Inheritance Strategy
 
-**All the capabilities of the parent theme will be `"passed"` to the child theme. For file-level conventions, child theme can override it by creating a file with the same name in the same location. For some theme configuration options, such as [globalLayout](./option-api.md/globallayout), child theme can override it by the same name configuration.**
+All the capabilities of the parent theme will be `"passed"` to the child theme. For file-level conventions, child theme can override it by creating a file with the same name in the same location. For some theme configuration options, such as [globalLayout](./option-api.md/globallayout), child theme can override it by the same name configuration.
 
-The [file-level agreement](./writing-a-theme.md#directory-structure) at are as follows:
+The [file-level conventions](./writing-a-theme.md#directory-structure) are as follows:
 
 - **Global Components**，i.e. the Vue components under `theme/global-components`.
 - **Components**，i.e. the Vue components under `theme/components`.
@@ -148,12 +148,12 @@ In this way, you can easily "tamper" with some part of an atomic theme.
 
 ::: tip
 1. You'd better override the component based on the code of the corresponding component in the parent theme.
-2. Currently, when developing theme locally, you need to manually restart dev serverwhen a component is created or removed.
+2. Currently, when developing theme locally, you need to manually restart dev server when a component is created or removed.
 :::
 
 ## Access Parent Theme
 
-You can use `@parent-theme` to access the root path of the parent theme. The following example shows creating a layout component with the same name in a child theme and simply using slots in the parent theme. [@vuepress/theme-vue](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/theme-vue) is created in this way based on the default theme.
+You can use `@parent-theme` to access the root path of the parent theme. The following example shows creating a layout component with the same name in a child theme and simply using slots in the parent theme. [@vuepress/theme-vue](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/theme-vue) is created in this way.
 
 ```vue
 <!-- themePath/components/Foo.vue -->

packages/docs/docs/theme/option-api.md

@@ -78,7 +78,7 @@ VuePress provides the ability to inherit one theme from another. VuePress will f
 **Also see:**
 
 - [Theme Inheritance](./inheritance.md)
-- [VuePress 1.x 的设计理念](../miscellaneous/design-concepts.md)
+- [Design Concepts of VuePress 1.x](../miscellaneous/design-concepts.md)
 
 ## globalLayout <Badge text="Danger Zone"/>
 

packages/docs/docs/zh/miscellaneous/glossary.md

@@ -58,7 +58,7 @@ sidebar: auto
 
 - Access: `Context.themeAPI.theme.path`
 
-当前使用的主题的所在路径（绝对路径）。
+当前使用的主题的所在的绝对路径。
 
 ## themeEntry
 
@@ -70,7 +70,7 @@ sidebar: auto
 
 - Access: `Context.themeAPI.parentTheme.path`
 
-如果当前使用的主题是一个派生主题，那么 `parentThemePath` 就是指父主题的所在路径（绝对路径）。
+如果当前使用的主题是一个派生主题，那么 `parentThemePath` 就是指父主题的所在绝对路径。
 
 ## parentThemeNetry
 

packages/docs/docs/zh/theme/inheritance.md

@@ -34,7 +34,7 @@ module.exports = {
 
 ## 继承策略
 
-**父主题的所有能力都会"传递"给子主题，对于文件级别的约定，子主题可以通过在同样的位置创建同名文件来覆盖它；对于某些主题配置选项，如 [globalLayout](./option-api.md#globallayout)，子主题也可以通过同名配置来覆盖它。**
+父主题的所有能力都会"传递"给子主题，对于文件级别的约定，子主题可以通过在同样的位置创建同名文件来覆盖它；对于某些主题配置选项，如 [globalLayout](./option-api.md#globallayout)，子主题也可以通过同名配置来覆盖它。
 
 [文件级别的约定](./writing-a-theme.md#目录结构)如下：
 
@@ -152,7 +152,7 @@ theme
 
 ## 访问父主题
 
-你可以使用 `@parent-theme` 来访问父主题的根路径，下述示例展示了在子主题中创建一个同名的布局组件，并简单使用父主题中的 slot，[@vuepress/theme-vue](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/theme-vue) 便是通过这种方式来基于默认主题创造的。
+你可以使用 `@parent-theme` 来访问父主题的根路径，下述示例展示了在子主题中创建一个同名的布局组件，并简单使用父主题中的 slot，[@vuepress/theme-vue](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/theme-vue) 便是通过这种方式创造的。
 
 ```vue
 <!-- themePath/components/Foo.vue -->