diff --git a/docs/fieldtypes/relationships.md b/docs/fieldtypes/relationships.md
index 5e7ac3b5a..e5506caf1 100755
--- a/docs/fieldtypes/relationships.md
+++ b/docs/fieldtypes/relationships.md
@@ -94,6 +94,7 @@ The following parameters are available to all looping relationship tags, allowin
 - `channel`
 - `entry_id`
 - `group_id`
+- `limit`
 - `offset`
 - `orderby`
 - `show_expired`
diff --git a/docs/member/password-validation.md b/docs/member/password-validation.md
index 9af2cc5b3..6cbbe20ef 100644
--- a/docs/member/password-validation.md
+++ b/docs/member/password-validation.md
@@ -17,7 +17,7 @@ It is recommended to select good a [password security policy](control-panel/sett
 
 ## Validation URL
 
-    `{exp:member:validation_url fields="password_rank"}`
+    {exp:member:validation_url fields="password_rank"}
 
 Return URL that is serving as the endpoint for validating member data and getting password rank. It can only accept POST requests sent via AJAX.
 It returns a JSON string that can contain following keys:
diff --git a/docs/templates/conditionals.md b/docs/templates/conditionals.md
index a5f7afd45..a28ccc1af 100755
--- a/docs/templates/conditionals.md
+++ b/docs/templates/conditionals.md
@@ -429,7 +429,7 @@ You can test against the username of the currently logged in user.
 
 Whether Multi-Factor Authentication is enabled for logged in user.
 
-    `{if !mfa_enabled}Enable multi-factor authentication for more security{/if}`
+    {if !mfa_enabled}Enable multi-factor authentication for more security{/if}
 
 ### `segment_*X*`