1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/content/zh-tw/books/porters-handbook/makefiles/chapter.adoc b/documentation/content/zh-tw/books/porters-handbook/makefiles/chapter.adoc
index 33ae230732..1ef7a4d813 100644
--- a/documentation/content/zh-tw/books/porters-handbook/makefiles/chapter.adoc
+++ b/documentation/content/zh-tw/books/porters-handbook/makefiles/chapter.adoc
@@ -87,7 +87,7 @@ When updating a port, it is possible to use man:pkg-version[8]'s `-t` argument t
 ====
 `pkg version -t` takes two versions as arguments, it will respond with `<`, `=` or `>` if the first version is less, equal, or more than the second version, respectively.
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 1.2 1.3
 < <.>
@@ -219,7 +219,7 @@ DISTVERSION=	1.2p4
 
 Both will generate a `PORTVERSION` of `1.2.p4` which is before than 1.2. man:pkg-version[8] can be used to check that fact:
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 1.2.p4 1.2
 <
@@ -241,7 +241,7 @@ PORTVERSION=	1.2p4
 
 In this case, using `DISTVERSION` is not possible because it would generate a version of `1.2.p4` which would be before `1.2` and not after. man:pkg-version[8] will verify this:
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 1.2 1.2.p4
 > <.>
@@ -297,7 +297,7 @@ From time to time a software vendor or FreeBSD porter will do something silly an
 
 The results of version number comparisons are not always obvious. `pkg version` (see man:pkg-version[8]) can be used to test the comparison of two version number strings. For example:
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 0.031 0.29
 >
@@ -1021,7 +1021,7 @@ BIND9 uses a version scheme that is not compatible with the ports versions (it h
 
 The order into which the ports framework, and pkg, will sort versions is checked using the `-t` argument of man:pkg-version[8]:
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 9.9.9 9.9.9.p1
 > <.>
@@ -1440,7 +1440,7 @@ GH_TAGNAME=	c472d66b
 
 This creates a versioning scheme that increases over time, and that is still before version `0` (see <<makefile-versions-ex-pkg-version>> for details on man:pkg-version[8]):
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t g20140411 0
 <
@@ -1456,7 +1456,7 @@ Which means using `PORTEPOCH` will not be needed in case upstream decides to cut
 
 If the current version of the software uses a Git tag, and the port needs to be updated to a newer, intermediate version, without a tag, use man:git-describe[1] to find out the version to use:
 
-[source,bash]
+[source,shell]
 ....
 % git describe --tags f0038b1
 v0.7.3-14-gf0038b1
@@ -1485,7 +1485,7 @@ USE_GITHUB=	yes
 
 This creates a versioning scheme that increases over time (well, over commits), and does not conflict with the creation of a `0.7.4` version. (See <<makefile-versions-ex-pkg-version>> for details on man:pkg-version[8]):
 
-[source,bash]
+[source,shell]
 ....
 % pkg version -t 0.7.3 0.7.3.14
 <
@@ -1497,7 +1497,7 @@ This creates a versioning scheme that increases over time (well, over commits),
 ****
 If the requested commit is the same as a tag, a shorter description is shown by default. The longer version is equivalent:
 
-[source,bash]
+[source,shell]
 ....
 % git describe --tags c66c71d
 v0.7.3
@@ -1635,7 +1635,7 @@ Using package:finance/moneymanagerex[] as an example, its GitHub repository is h
 
 The only information missing from that file is the commit hash or tag to use as a version. This information is found after cloning the repository:
 
-[source,bash]
+[source,shell]
 ....
 % git clone --recurse-submodules https://github.com/moneymanagerex/moneymanagerex.git
 Cloning into 'moneymanagerex'...
@@ -4588,7 +4588,7 @@ The most common content of one of these variable is the package base of another
 
 package:dns/bind99[] cannot be installed if package:dns/bind910[] is present because they install same files. First gather the package base to use:
 
-[source,bash]
+[source,shell]
 ....
 % make -C dns/bind99 -V PKGBASE
 bind99