summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDuncan Mac-Vicar P <dmacvicar@suse.de>2017-11-24 17:11:39 +0100
committerDuncan Mac-Vicar P <dmacvicar@suse.de>2017-11-24 17:56:45 +0100
commit9f7f0253a320a3fe96c2970fa486064fd7cb3963 (patch)
tree2af08467c51e8b55af7facc54dab8bcc7a18f326
parentc3aad57b10355410bc3e897ba47ac916992cf626 (diff)
downloadterraform-provider-libvirt-9f7f0253a320a3fe96c2970fa486064fd7cb3963.tar
terraform-provider-libvirt-9f7f0253a320a3fe96c2970fa486064fd7cb3963.tar.gz
Typo
-rw-r--r--website/docs/r/domain.html.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/website/docs/r/domain.html.markdown b/website/docs/r/domain.html.markdown
index 2a0e50e8..f008501e 100644
--- a/website/docs/r/domain.html.markdown
+++ b/website/docs/r/domain.html.markdown
@@ -167,7 +167,7 @@ read-only.
domain. However, `libvirt` can manage this automatically (and this is the recommended solution)
if a mapping for the firmware to a _variables file_ exists in `/etc/libvirt/qemu.conf:nvram`.
In that case, `libvirt` will copy that variables file into a file specific for this domain.
-s * `template` - (Optional) path to the file used to override variables from the master NVRAM
+ * `template` - (Optional) path to the file used to override variables from the master NVRAM
store.
So you should typically use the firmware as this,