Wrapped code block's files with curly braces

Signed-off-by: Ihor Aleksandrychiev <ihor.aleksandrychiev@northern.tech>

Author: aleksandrychev

cheatsheet.markdown

@@ -276,7 +276,7 @@ These two blocks will be joined into one element on the UI.
 You can specify file name of the code block by adding  `[file=Name of the file]` in the first line.
 This line won't be shown in the resulting HTML (it will be converted to the heading / frame).
 
-```cf3 file=policy.cf
+```cf3 {file="policy.cf"}
 bundle agent hello_world
 {
   meta:

examples.markdown

@@ -106,7 +106,7 @@ Go back into vi by typing "vi" at the prompt. Then type ```i``` to insert
  __body common control__ to `hello_world.cf`. Place it above __bundle agent hello_world__, as
 shown in the following example:
 
-```cf3 file=hello_world.cf
+```cf3 {file="hello_world.cf"}
 body common control
 {
   bundlesequence => { "hello_world" };
@@ -135,7 +135,7 @@ notice: R: Hello World!
 **Note:** It may be necessary to add a reference to the standard library within the body common control section, and remove the `bundlesequence` line.
 Example:
 
-```cf3 file=hello_world.cf
+```cf3 {file="hello_world.cf"}
 body common control
 {
   inputs => {
@@ -155,7 +155,7 @@ Again type "vi" then "Enter" then ```i``` to insert the following:
 
 Add it before __body common control__, as shown below:
 
-```cf3 file=hello_world.cf
+```cf3 {file="hello_world.cf"}
 #!/var/cfengine/bin/cf-agent --no-lock
 body common control
 {

examples/example-snippets/promise-patterns/example_ssh_keys.markdown

@@ -14,7 +14,7 @@ the [Masterfiles Policy Framework][Masterfiles Policy Framework]. The
 you do not have a `def.json` in the root of your masterfiles directory
 simply create it with the following content.
 
-```json file=def.json
+```json {file="def.json"}
 {
   "classes": {
                "services_autorun": [ "any" ]

examples/tutorials/custom_inventory.markdown

@@ -46,7 +46,7 @@ information we will write an inventory policy to report that information.
 Create `/var/cfengine/masterfiles/services/tutorials/inventory/owner.cf` with the
 following content:
 
-```cf3 file=owner.cf
+```cf3 {file="owner.cf"}
 bundle agent tutorials_inventory_owner
 # @brief Inventory Owner information
 # @description Inventory owner information from `/vagrant/inventory_owner.csv`.

examples/tutorials/distribute-files-from-a-central-location.markdown

@@ -47,7 +47,7 @@ These variables provide path definitions for storing and deploying patches.
 
 Add the following variable information to the `masterfiles/def.cf` file:
 
-```cf3 file=def.cf
+```cf3 {file="def.cf"}
 "dir_patch_store"
   string => "/storage/patches",
   comment => "Define patch files source location",
@@ -74,7 +74,7 @@ promise type in a `server` bundle. The default access rules defined by the MPF (
 
 There is no need to modify the vendored policy, instead define your own server bundle. For our example, add the following to `services/main.cf`:
 
-```cf3 file=main.cf
+```cf3 {file="main.cf"}
 bundle server my_access_rules
 {
   access:
@@ -93,7 +93,7 @@ use is a good idea. This information is stored in a custom library.
 
 Create a custom library called `lib/custom/files.cf`. Add the following content:
 
-```cf3 file=files.cf
+```cf3 {file="files.cf"}
 bundle agent sync_from_policyserver(source_path, dest_path)
 # @brief Sync files from the policy server to the agent
 #
@@ -118,7 +118,7 @@ policy by services.
 
 Create `services/patching.cf` with the following content:
 
-```cf3 file=patching.cf
+```cf3 {file="patching.cf"}
 # Patching Policy
 
 bundle agent patching

examples/tutorials/files-tutorial.markdown

@@ -84,7 +84,7 @@ Note: The following workflow assumes the directory /home/user already exists. If
 
 ## Create a File
 
-```cf3 file=file_create.cf
+```cf3 {file="file_create.cf"}
 bundle agent testbundle
 {
   files:
@@ -125,7 +125,7 @@ rm /home/user/test_plain.txt
 
 ## Delete a File
 
-```cf3 file=file_delete.cf
+```cf3 {file="file_delete.cf"}
 body common control
 {
   inputs => {
@@ -191,7 +191,7 @@ ls /home/user/test_plain.txt
 /var/cfengine/bin/cf-agent --no-lock --file ./file_test.cf --bundlesequence list_file,list_file_2
 ```
 
-```cf3 file=file_modify.cf
+```cf3 {file="file_modify.cf"}
 body common control
 {
   inputs => {
@@ -289,7 +289,7 @@ rm /home/user/test_plain.txt
 
 ## Copy a file and edit its text
 
-```cf3 file=file_copy.cf
+```cf3 {file="file_copy.cf"}
 body common control
 {
   inputs => {

examples/tutorials/integrating-alerts-with-pager-duty.markdown

@@ -28,7 +28,7 @@ touch /tmp/file-integrity
 
 Insert the following policy into `/tmp/file_example.cf`
 
-```cf3 file=file_example.cf
+```cf3 {file="file_example.cf"}
 bundle agent file_integrity
 {
   files:

examples/tutorials/integrating-with-sumo-logic.markdown

@@ -158,7 +158,7 @@ As we can see above CFEngine detected a change on `Thursday Oct 2 at 01:16:42` a
 
 The policy as found in `sumologic_policy_update.cf`.
 
-```cf3 file=sumo_logic_policy_update.cf
+```cf3 {file="sumo_logic_policy_update.cf"}
 bundle agent sumo_logic_policy_update
 {
   vars:

examples/tutorials/json-yaml-support-in-cfengine.markdown

@@ -76,7 +76,7 @@ expressions or class names.
 
 Easy, right?
 
-```cf3 file=json_example.cf
+```cf3 {file="json_example.cf"}
 body common control
 {
       bundlesequence => { "run" };

examples/tutorials/manage-local-users.markdown

@@ -30,7 +30,7 @@ Create user group security and webadmin.
 
 Create a file `/tmp/users.cf` with the following content:
 
-```cf3 file=users.cf
+```cf3 {file="users.cf"}
 body common control
 {
   inputs => { "$(sys.libdir)/stdlib.cf" };