Improving docs for salt.states.cron

salt/states/cron.py

@@ -50,7 +50,7 @@ then a new cron job will be added to the user's crontab.
 
 The current behavior is still relying on that mechanism, but you can also
 specify an identifier to identify your crontabs:
-.. versionadded:: 2014.2
+
 .. code-block:: yaml
 
     date > /tmp/crontest:
@@ -60,8 +60,10 @@ specify an identifier to identify your crontabs:
         - minute: 7
         - hour: 2
 
+.. versionadded:: 2014.1.2
+
 And, some months later, you modify it:
-.. versionadded:: 2014.2
+
 .. code-block:: yaml
 
     superscript > /tmp/crontest:
@@ -71,6 +73,8 @@ And, some months later, you modify it:
         - minute: 3
         - hour: 4
 
+.. versionadded:: 2014.1.2
+
 The old **date > /tmp/crontest** will be replaced by
 **superscript > /tmp/crontest**.
 
@@ -376,7 +380,7 @@ def file(name,
         hosted on either the salt master server, or on an HTTP or FTP server.
         For files hosted on the salt file server, if the file is located on
         the master in the directory named spam, and is called eggs, the source
-        string is salt://spam/eggs.
+        string is ``salt://spam/eggs``
 
         If the file is hosted on a HTTP or FTP server then the source_hash
         argument is also required
@@ -385,7 +389,7 @@ def file(name,
         This can be either a file which contains a source hash string for
         the source, or a source hash string. The source hash string is the
         hash algorithm followed by the hash of the file:
-        md5=e138491e9d5b97023cea823fe17bac22
+        ``md5=e138491e9d5b97023cea823fe17bac22``
 
     user
         The user to whom the crontab should be assigned. This defaults to