Change iscsiscan invocation in pve-storage-iscsi

[pve-docs.git] / pct.adoc

diff --git a/pct.adoc b/pct.adoc
index 6735406b86be901dded26a0bb063344b83cbaa44..9fa6a3822974fefd7dba1b32cd45b292e3dc71bd 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -143,7 +143,7 @@ and will not be moved.
 Modification of a file can be prevented by adding a `.pve-ignore.`
 file for it.  For instance, if the file `/etc/.pve-ignore.hosts`
 exists then the `/etc/hosts` file will not be touched. This can be a
-simple empty file creatd via:
+simple empty file created via:
 
  # touch /etc/.pve-ignore.hosts
 
@@ -323,17 +323,17 @@ group/others model.
 Backup of Containers mount points
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default additional mount points besides the RootDisk mount point are not
-included in backups. You can reverse this default behavior by setting the 
-* Backup* option on a mount point.
+By default additional mount points besides the Root Disk mount point are not
+included in backups. You can reverse this default behavior by setting the
+*Backup* option on a mount point.
 // see PVE::VZDump::LXC::prepare()
 
 Replication of Containers mount points
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default additional mount points are replicated when the RootDisk 
+By default additional mount points are replicated when the Root Disk
 is replicated. If you want the {pve} storage replication mechanism to skip a
- mount point when starting  a replication job, you can set the 
+ mount point when starting  a replication job, you can set the
 *Skip replication* option on that mount point. +
 As of {pve} 5.0, replication requires a storage of type `zfspool`, so adding a
  mount point to a different type of storage when the container has replication
@@ -348,7 +348,7 @@ Container Settings
 General Settings
 ~~~~~~~~~~~~~~~~
 
-[thumbnail="gui-create-ct-general.png"]
+[thumbnail="screenshot/gui-create-ct-general.png"]
 
 General settings of a container include
 
@@ -393,7 +393,7 @@ or greater than 220.
 CPU
 ~~~
 
-[thumbnail="gui-create-ct-cpu.png"]
+[thumbnail="screenshot/gui-create-ct-cpu.png"]
 
 You can restrict the number of visible CPUs inside the container using
 the `cores` option. This is implemented using the Linux 'cpuset'
@@ -438,7 +438,7 @@ prioritize some containers.
 Memory
 ~~~~~~
 
-[thumbnail="gui-create-ct-memory.png"]
+[thumbnail="screenshot/gui-create-ct-memory.png"]
 
 Container memory is controlled using the cgroup memory controller.
 
@@ -457,7 +457,7 @@ swap`).
 Mount Points
 ~~~~~~~~~~~~
 
-[thumbnail="gui-create-ct-root-disk.png"]
+[thumbnail="screenshot/gui-create-ct-root-disk.png"]
 
 The root mount point is configured with the `rootfs` property, and you can
 configure up to 10 additional mount points. The corresponding options
@@ -545,7 +545,7 @@ NOTE: The contents of device mount points are not backed up when using `vzdump`.
 Network
 ~~~~~~~
 
-[thumbnail="gui-create-ct-network.png"]
+[thumbnail="screenshot/gui-create-ct-network.png"]
 
 You can configure up to 10 network interfaces for a single
 container. The corresponding options are called `net0` to `net9`, and
@@ -567,7 +567,7 @@ the following command:
 
 .Start and Shutdown Order
 // use the screenshot from qemu - its the same
-[thumbnail="gui-qemu-edit-start-order.png"]
+[thumbnail="screenshot/gui-qemu-edit-start-order.png"]
 
 If you want to fine tune the boot order of your containers, you can use the following
 parameters :