1 files changed, 28 insertions, 20 deletions
diff --git a/documentation/content/zh-tw/books/porters-handbook/upgrading/chapter.adoc b/documentation/content/zh-tw/books/porters-handbook/upgrading/chapter.adoc
index fc39415577..ce72ab3f4c 100644
--- a/documentation/content/zh-tw/books/porters-handbook/upgrading/chapter.adoc
+++ b/documentation/content/zh-tw/books/porters-handbook/upgrading/chapter.adoc
@@ -11,32 +11,40 @@ next: books/porters-handbook/security
 :toclevels: 1
 :icons: font
 :sectnums:
+:sectnumlevels: 6
+:sectnumoffset: 11
+:partnums:
 :source-highlighter: rouge
 :experimental:
-:skip-front-matter:
-:toc-title: 目录
-:part-signifier: 部分
-:chapter-signifier: 第
-:appendix-caption: 附录
-:table-caption: 表
-:figure-caption: 图
-:example-caption: 例 
-:xrefstyle: basic
-:relfileprefix: ../
-:outfilesuffix:
-:sectnumoffset: 11
+:images-path: books/porters-handbook/
 
-include::shared/mirrors.adoc[]
+ifdef::env-beastie[]
+ifdef::backend-html5[]
+:imagesdir: ../../../../images/{images-path}
+endif::[]
+ifndef::book[]
 include::shared/authors.adoc[]
+include::shared/mirrors.adoc[]
 include::shared/releases.adoc[]
-include::shared/zh-tw/mailing-lists.adoc[]
-include::shared/zh-tw/urls.adoc[]
+include::shared/attributes/attributes-{{% lang %}}.adoc[]
+include::shared/{{% lang %}}/teams.adoc[]
+include::shared/{{% lang %}}/mailing-lists.adoc[]
+include::shared/{{% lang %}}/urls.adoc[]
+toc::[]
+endif::[]
+ifdef::backend-pdf,backend-epub3[]
+include::../../../../../shared/asciidoctor.adoc[]
+endif::[]
+endif::[]
 
+ifndef::env-beastie[]
 toc::[]
+include::../../../../../shared/asciidoctor.adoc[]
+endif::[]
 
 When a port is not the most recent version available from the authors, update the local working copy of [.filename]#/usr/ports#. The port might have already been updated to the new version.
 
-When working with more than a few ports, it will probably be easier to use Subversion to keep the whole ports collection up-to-date, as described in the link:{handbook}#ports-using/[Handbook]. This will have the added benefit of tracking all the port's dependencies.
+When working with more than a few ports, it will probably be easier to use Subversion to keep the whole ports collection up-to-date, as described in the extref:{handbook}ports/[Handbook, ports-using]. This will have the added benefit of tracking all the port's dependencies.
 
 The next step is to see if there is an update already pending. To do this, there are two options. There is a searchable interface to the https://bugs.freebsd.org/search/[FreeBSD Problem Report (PR) or bug database]. Select `Ports & Packages` in the `Product` multiple select menu, and enter the name of the port in the `Summary` field.
 
@@ -62,11 +70,11 @@ If some files have been added, copied, moved, or removed, add this information t
 
 To simplify common operations with patch files, use `make makepatch` as described in <<slow-patch>>. Other tools exists, like [.filename]#/usr/ports/Tools/scripts/patchtool.py#. Before using it, please read [.filename]#/usr/ports/Tools/scripts/README.patchtool#.
 
-If the port is unmaintained, and you are actively using it, please consider volunteering to become its maintainer. FreeBSD has over 4000 ports without maintainers, and this is an area where more volunteers are always needed. (For a detailed description of the responsibilities of maintainers, refer to the section in the link:{developers-handbook}#POLICIES-MAINTAINER[Developer's Handbook].)
+If the port is unmaintained, and you are actively using it, please consider volunteering to become its maintainer. FreeBSD has over 4000 ports without maintainers, and this is an area where more volunteers are always needed. (For a detailed description of the responsibilities of maintainers, refer to the section in the extref:{developers-handbook}[Developer's Handbook]., POLICIES-MAINTAINER)
 
 To submit the diff, use the https://bugs.freebsd.org/submit/[bug submit form] (product `Ports & Packages`, component `Individual Port(s)`). Always include the category with the port name, followed by colon, and brief descripton of the issue. Examples: `_category/portname_: _add FOO option_`; `_category/portname_: _Update to X.Y_`. Please mention any added or deleted files in the message, as they have to be explicitly specified to man:svn[1] when doing a commit. Do not compress or encode the diff.
 
-Before submitting the bug, review the link:{problem-reports}#pr-writing/[ Writing the problem report] section in the Problem Reports article. It contains far more information about how to write useful problem reports.
+Before submitting the bug, review the extref:{problem-reports}#pr-writing/[ Writing the problem report] section in the Problem Reports article. It contains far more information about how to write useful problem reports.
 
 [IMPORTANT]
 ====
@@ -94,7 +102,7 @@ When possible, please submit a man:svn[1] diff. They are easier to handle than d
 
 <.> This can be anywhere, of course. Building ports is not limited to within [.filename]#/usr/ports/#.
 
-<.> https://svn.FreeBSD.org/[svn.FreeBSD.org] is the FreeBSD public Subversion server. See link:{handbook}#svn-mirrors[Subversion mirror sites] for more information.
+<.> https://svn.FreeBSD.org/[svn.FreeBSD.org] is the FreeBSD public Subversion server. See extref:{handbook}mirrors[Subversion mirror sites, svn-mirrors] for more information.
 
 While in the port directory, make any changes that are needed. If adding, copying, moving, or removing a file, use `svn` to track these changes:
 
@@ -147,7 +155,7 @@ The last step is to make a unified man:diff[1] of the changes:
 If files have been added, copied, moved, or removed, include the man:svn[1] `add`, `copy`, `move`, and `remove` commands that were used. `svn move` or `svn copy` must be run before the patch can be applied. `svn add` or `svn remove` must be run after the patch is applied.
 ====
 
-Send the patch following the link:{problem-reports}#pr-writing/[problem report submission guidelines].
+Send the patch following the extref:{problem-reports}[problem report submission guidelines, pr-writing].
 
 [[moved-and-updating-files]]
 == [.filename]#UPDATING# and [.filename]#MOVED#