improve md

docs/recipes/retry.md

@@ -16,11 +16,11 @@
   ]
 }
 -->
-## Retry ##
+# Retry
 
 This document explains how to use retry functionality with some simple examples.
 
-### Example 1: ###
+## Example 1
 
 ```luceescript
 // example1.cfm
@@ -46,7 +46,7 @@ In this example, we have the "try" and "catch" blocks for reading a file and out
 
 This is not the best way. 'Retry' is a better option. The retry code looks like example2.cfm
 
-### Example 2: ###
+## Example 2
 
 ```luceescript
 // example2.cfm
@@ -69,7 +69,7 @@ In this example, we use the retry functionality. Here we also still check if the
 
 We do not get an exception because if the file does not exist, we call retry (read the file again and output the file content). For this case, we simply use retry, and if it fails, we correct what is wrong.
 
-### Footnotes ###
+## Footnotes
 
 Here you can see these details in the video also:
 

docs/recipes/s3.md

@@ -15,11 +15,11 @@
   ]
 }
 -->
-## S3 for source code ##
+# Using S3 directly for source code
 
 This document explains how to use S3 as for your source code and how to use S3 for your artifacts when we look at the source code itself.
 
-### Example:
+## Example:
 
 ```luceescript
 // get an image directly from s3
@@ -65,7 +65,7 @@ But again, that would expose your credentials for everybody that sees an excepti
 
 It might be very useful to schedule a task that checks every five minutes or so to see if there are changes in the files on S3, and flush everything is there are changes.
 
-### Footnotes ###
+## Footnotes
 
 Here you can also see these details in the video: