scan-adoc-refs: factor out register_title

[pve-docs.git] / pve-storage-nfs.adoc

diff --git a/pve-storage-nfs.adoc b/pve-storage-nfs.adoc
index 7e08f7f712e54fb5d54e9312c1d9cfb95fe2aab8..6165dc75c68ae58b9deb0ccfb09d18feec806374 100644 (file)
--- a/pve-storage-nfs.adoc
+++ b/pve-storage-nfs.adoc
@@ -2,6 +2,10 @@ NFS Backend
 -----------
 include::attributes.txt[]
 
+ifdef::wiki[]
+:pve-toplevel:
+endif::wiki[]
+
 Storage pool type: `nfs`
 
 The NFS backend is based on the directory backend, so it shares most
@@ -22,7 +26,7 @@ used to configure the NFS server:
 server::
 
 Server IP or DNS name. To avoid DNS lookup delays, it is usually
-preferrable to use an IP address instead of a DNS name - unless you
+preferable to use an IP address instead of a DNS name - unless you
 have a very reliable DNS server, or list the server in the local
 `/etc/hosts` file.
 
@@ -59,7 +63,7 @@ client side. For read-only content, it is worth to consider the NFS
 Storage Features
 ~~~~~~~~~~~~~~~~
 
-NFS does not support snapshots, but the backend use `qcow2` features
+NFS does not support snapshots, but the backend uses `qcow2` features
 to implement snapshots and cloning.
 
 .Storage features for backend `nfs`