doc: remove backtick escaping for manpage refs

Removing backticks will make the doctool emit links to the man pages.

PR-URL: #9632
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Jeremiah Senkpiel <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

doc/api/child_process.md

@@ -776,7 +776,7 @@ added: v0.1.90
 * `signal` {String}
 
 The `child.kill()` methods sends a signal to the child process. If no argument
-is given, the process will be sent the `'SIGTERM'` signal. See `signal(7)` for
+is given, the process will be sent the `'SIGTERM'` signal. See signal(7) for
 a list of available signals.
 
 ```js

doc/api/console.md

@@ -184,7 +184,7 @@ added: v0.1.100
 
 Prints to `stderr` with newline. Multiple arguments can be passed, with the
 first used as the primary message and all additional used as substitution
-values similar to `printf(3)` (the arguments are all passed to
+values similar to printf(3) (the arguments are all passed to
 [`util.format()`][]).
 
 ```js
@@ -213,7 +213,7 @@ added: v0.1.100
 
 Prints to `stdout` with newline. Multiple arguments can be passed, with the
 first used as the primary message and all additional used as substitution
-values similar to `printf(3)` (the arguments are all passed to
+values similar to printf(3) (the arguments are all passed to
 [`util.format()`][]).
 
 ```js

doc/api/dns.md

@@ -394,14 +394,14 @@ Under the hood, [`dns.lookup()`][] uses the same operating system facilities
 as most other programs. For instance, [`dns.lookup()`][] will almost always
 resolve a given name the same way as the `ping` command. On most POSIX-like
 operating systems, the behavior of the [`dns.lookup()`][] function can be
-modified by changing settings in `nsswitch.conf(5)` and/or `resolv.conf(5)`,
+modified by changing settings in nsswitch.conf(5) and/or resolv.conf(5),
 but note that changing these files will change the behavior of _all other
 programs running on the same operating system_.
 
 Though the call to `dns.lookup()` will be asynchronous from JavaScript's
-perspective, it is implemented as a synchronous call to `getaddrinfo(3)` that
+perspective, it is implemented as a synchronous call to getaddrinfo(3) that
 runs on libuv's threadpool. Because libuv's threadpool has a fixed size, it
-means that if for whatever reason the call to `getaddrinfo(3)` takes a long
+means that if for whatever reason the call to getaddrinfo(3) takes a long
 time, other operations that could run on libuv's threadpool (such as filesystem
 operations) will experience degraded performance. In order to mitigate this
 issue, one potential solution is to increase the size of libuv's threadpool by
@@ -412,7 +412,7 @@ setting the `'UV_THREADPOOL_SIZE'` environment variable to a value greater than
 ### `dns.resolve()`, `dns.resolve*()` and `dns.reverse()`
 
 These functions are implemented quite differently than [`dns.lookup()`][]. They
-do not use `getaddrinfo(3)` and they _always_ perform a DNS query on the
+do not use getaddrinfo(3) and they _always_ perform a DNS query on the
 network. This network communication is always done asynchronously, and does not
 use libuv's threadpool.
 

doc/api/fs.md

@@ -212,21 +212,21 @@ page.
 The times in the stat object have the following semantics:
 
 * `atime` "Access Time" - Time when file data last accessed.  Changed
-  by the `mknod(2)`, `utimes(2)`, and `read(2)` system calls.
+  by the mknod(2), utimes(2), and read(2) system calls.
 * `mtime` "Modified Time" - Time when file data last modified.
-  Changed by the `mknod(2)`, `utimes(2)`, and `write(2)` system calls.
+  Changed by the mknod(2), utimes(2), and write(2) system calls.
 * `ctime` "Change Time" - Time when file status was last changed
-  (inode data modification).  Changed by the `chmod(2)`, `chown(2)`,
-  `link(2)`, `mknod(2)`, `rename(2)`, `unlink(2)`, `utimes(2)`,
-  `read(2)`, and `write(2)` system calls.
+  (inode data modification).  Changed by the chmod(2), chown(2),
+  link(2), mknod(2), rename(2), unlink(2), utimes(2),
+  read(2), and write(2) system calls.
 * `birthtime` "Birth Time" -  Time of file creation. Set once when the
   file is created.  On filesystems where birthtime is not available,
   this field may instead hold either the `ctime` or
   `1970-01-01T00:00Z` (ie, unix epoch timestamp `0`). Note that this
   value may be greater than `atime` or `mtime` in this case. On Darwin
   and other FreeBSD variants, also set if the `atime` is explicitly
   set to an earlier value than the current `birthtime` using the
-  `utimes(2)` system call.
+  utimes(2) system call.
 
 Prior to Node v0.12, the `ctime` held the `birthtime` on Windows
 systems.  Note that as of v0.12, `ctime` is not "creation time", and

doc/api/readline.md

@@ -207,7 +207,7 @@ added: v0.7.5
 **This does not work on Windows.**
 
 Emitted whenever the `input` stream is sent to the background with `^Z`,
-respectively known as `SIGTSTP`, and then continued with `fg(1)`. This event
+respectively known as `SIGTSTP`, and then continued with fg(1). This event
 only emits if the stream was not paused before sending the program to the
 background.
 

doc/api/repl.md

@@ -359,7 +359,7 @@ connect to a long-running Node.js process without restarting it.
 For an example of running a "full-featured" (`terminal`) REPL over
 a `net.Server` and `net.Socket` instance, see: https://gist.github.com/2209310
 
-For an example of running a REPL instance over `curl(1)`,
+For an example of running a REPL instance over curl(1),
 see: https://gist.github.com/2053342
 
 [`readline.prompt`]: readline.html#readline_rl_prompt_preservecursor