Extend VMWare image provisioning documentation

[lbayerlein]

Extend VMWare documentation. Image provisioning information without ssh - extend finish information as new bullet point

[lbayerlein]

If my way of documentation is ok, I can add it to latest, too. In future, should I do this the other way round? (first latest, then 1.x)

[tbrisker]

@ezr-ondrej can you please take a look?
@lbayerlein either way is fine, normally we start with nightly since that's the next release and sometimes documentation changes are related to things that are only present in the nightlies, but in the case of improving existing documentation the order doesn't matter, as long as we update both.

[ezr-ondrej]

Just a bit of more fancy wording, I suggested some, but not a native speaker, so no hard feelings if you don't agree, but otherwise nice addition, thanks 👍

[lbayerlein]

Ok I will do an update to the latest documentation, too. I will take the new fancy words for that :)

[lzap]

What's the status?

[lzap]

Ok lemme squash this, thank you!

[lzap]

Okay this needs to be rebased and single commit and the change must be done against the nightly file, can you do that please?

diff --git a/_includes/manuals/nightly/5.2.8_cr_vmware.md b/_includes/manuals/nightly/5.2.8_cr_vmware.md
index fcb79a736..12d4ee561 100644
--- a/_includes/manuals/nightly/5.2.8_cr_vmware.md
+++ b/_includes/manuals/nightly/5.2.8_cr_vmware.md
@@ -17,6 +17,7 @@ The same process can also be done using a user_data template. To configure image
 * Browse then to the image to be used for provisioning, and ensure that "User Data" is checked
 * Associate a user_data template to the host. The template will use cloud-init syntax.
 * Note that the images don't need cloudinit installed, as the cloudinit is converted under the hood to a CustomisationSpec object that VMware can process
+* In order to inform foreman about successful build and get the host to "Installed" state in the UI, the provisioned host have to run a finish script. You can

Thanks!