Use correct syntax markup for shell

Approved by:	carlavilla

documentation/content/pl/books/handbook/linuxemu/_index.adoc

@@ -75,21 +75,21 @@ By default, Linux(R) libraries are not installed and Linux(R) binary compatibili
 
 Before attempting to build the port, load the Linux(R) kernel module, otherwise the build will fail:
 
-[source,bash]
+[source,shell]
 ....
 # kldload linux
 ....
 
 For 64-bit compatibility:
 
-[source,bash]
+[source,shell]
 ....
 # kldload linux64
 ....
 
 To verify that the module is loaded:
 
-[source,bash]
+[source,shell]
 ....
 % kldstat
       Id Refs Address    Size     Name
@@ -99,7 +99,7 @@ To verify that the module is loaded:
 
 The package:emulators/linux_base-c7[] package or port is the easiest way to install a base set of Linux(R) libraries and binaries on a FreeBSD system. To install the port:
 
-[source,bash]
+[source,shell]
 ....
 # pkg install emulators/linux_base-c7
 ....
@@ -122,7 +122,7 @@ If a Linux(R) application complains about missing shared libraries after configu
 
 From a Linux(R) system, `ldd` can be used to determine which shared libraries the application needs. For example, to check which shared libraries `linuxdoom` needs, run this command from a Linux(R) system that has Doom installed:
 
-[source,bash]
+[source,shell]
 ....
 % ldd linuxdoom
 libXt.so.3 (DLL Jump 3.1) => /usr/X11/lib/libXt.so.3.1.0
@@ -132,7 +132,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29
 
 Then, copy all the files in the last column of the output from the Linux(R) system into [.filename]#/compat/linux# on the FreeBSD system. Once copied, create symbolic links to the names in the first column. This example will result in the following files on the FreeBSD system:
 
-[source,bash]
+[source,shell]
 ....
 /compat/linux/usr/X11/lib/libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libXt.so.3 -> libXt.so.3.1.0
@@ -146,7 +146,7 @@ If a Linux(R) shared library already exists with a matching major revision numbe
 
 For example, these libraries already exist on the FreeBSD system:
 
-[source,bash]
+[source,shell]
 ....
 /compat/linux/lib/libc.so.4.6.27
 /compat/linux/lib/libc.so.4 -> libc.so.4.6.27
@@ -154,14 +154,14 @@ For example, these libraries already exist on the FreeBSD system:
 
 and `ldd` indicates that a binary requires a later version:
 
-[source,bash]
+[source,shell]
 ....
 libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29
 ....
 
 Since the existing library is only one or two versions out of date in the last digit, the program should still work with the slightly older version. However, it is safe to replace the existing [.filename]#libc.so# with the newer version:
 
-[source,bash]
+[source,shell]
 ....
 /compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29
@@ -173,7 +173,7 @@ Generally, one will need to look for the shared libraries that Linux(R) binaries
 
 ELF binaries sometimes require an extra step. When an unbranded ELF binary is executed, it will generate an error message:
 
-[source,bash]
+[source,shell]
 ....
 % ./my-linux-elf-binary
 ELF binary type not known
@@ -182,7 +182,7 @@ Abort
 
 To help the FreeBSD kernel distinguish between a FreeBSD ELF binary and a Linux(R) binary, use man:brandelf[1]:
 
-[source,bash]
+[source,shell]
 ....
 % brandelf -t Linux my-linux-elf-binary
 ....
@@ -193,7 +193,7 @@ Since the GNU toolchain places the appropriate branding information into ELF bin
 
 To install a Linux(R) RPM-based application, first install the package:archivers/rpm4[] package or port. Once installed, `root` can use this command to install a [.filename]#.rpm#:
 
-[source,bash]
+[source,shell]
 ....
 # cd /compat/linux
 # rpm2cpio < /path/to/linux.archive.rpm | cpio -id
@@ -205,7 +205,7 @@ If necessary, `brandelf` the installed ELF binaries. Note that this will prevent
 
 If DNS does not work or this error appears:
 
-[source,bash]
+[source,shell]
 ....
 resolv+: "bind" is an invalid keyword resolv+:
 "hosts" is an invalid keyword
@@ -240,7 +240,7 @@ For the Linux(R) ABI support, FreeBSD sees the magic number as an ELF binary. Th
 
 For Linux(R) binaries to function, they must be _branded_ as type `Linux` using man:brandelf[1]:
 
-[source,bash]
+[source,shell]
 ....
 # brandelf -t Linux file
 ....