doc: cleanup includes files after CamelCase fix

docs/manuals/source/manually_added_config_directive_descriptions/dir-fileset-EnableVSS.rst.inc

@@ -0,0 +1,2 @@
+:index:`\ <single: Windows; Enable VSS>`\  If this directive is set to :strong:`yes` the File daemon will be notified that the user wants to use a Volume Shadow Copy Service (VSS) backup for this job. This directive is effective only on the Windows File Daemon. It permits a consistent copy of open files to be made for cooperating writer applications, and for applications that are not VSS away, Bareos can at least copy open files. The Volume Shadow Copy will only be done on
+Windows drives where the drive (e.g. C:, D:, ...) is explicitly mentioned in a :strong:`File`\  directive. For more information, please see the :ref:`Windows <VSS>` chapter of this manual.

docs/manuals/source/manually_added_config_directive_descriptions/sd-storage-AutoXFlateOnReplication.rst.inc

@@ -0,0 +1,2 @@
+This directive controls the :ref:`autoxflate-sd plugin <plugin-autoxflate-sd>` plugin when replicating data inside one or between two storage daemons (Migration/Copy Jobs). Normally the storage daemon will use the autoinflate/autodeflate setting of the device when reading and writing data to it which could mean that while reading it inflates the compressed data and the while writing the other deflates it again. If you just want the data to be exactly the same e.g. don’t perform any
+on the fly uncompression and compression while doing the replication of data you can set this option to no and it will override any setting on the device for doing auto inflation/deflation when doing data replication. This will not have any impact on any normal backup or restore jobs.