diff --git a/_articles/miscellaneous/custom-fields.md b/_articles/miscellaneous/custom-fields.md
index 06ab8d72..846f5d1d 100644
--- a/_articles/miscellaneous/custom-fields.md
+++ b/_articles/miscellaneous/custom-fields.md
@@ -22,7 +22,7 @@ If one of these matches is found, bitwarden will auto-fill the custom field's va
 
 ## Special name prefixes for auto-filling
 
-When bitwarden searches for a webpage's form element to match with your custom field's name, an exact, case-insensitive comparison is done. For example, if your custom field has the name `PIN`, the following form element's values (from the id, name, label, etc) will match for auto-filling: "pin", "PIN", and "Pin". However, values such as "pin2" or "mypin" will not match.
+When bitwarden searches for a webpage's form element to match with your custom field's name, an exact, case-insensitive comparison is done. For example, if your custom field has the name "PIN", the following form element's values (from the id, name, label, etc) will match for auto-filling: "pin", "PIN", and "Pin". However, values such as "pin2" or "mypin" will not match.
 
 There are two special name prefixes that can give you even more control over how your custom field is auto-filled:
 
@@ -36,7 +36,7 @@ Example:
 
 **Regular Expressions**
 
-Prefixing your custom field's name with `regex=` allows you to perform regular expression comparisons when an auto-fill is performed.
+Prefixing your custom field's name with `regex=` allows you to perform [regular expression](https://regexone.com/){:target="_blank"} comparisons when an auto-fill is performed.
 
 Example: