diff --git a/documentation/modules/exploit/linux/samba/is_known_pipename.md b/documentation/modules/exploit/linux/samba/is_known_pipename.md
index 4ef19bfe52..0757631b87 100644
--- a/documentation/modules/exploit/linux/samba/is_known_pipename.md
+++ b/documentation/modules/exploit/linux/samba/is_known_pipename.md
@@ -18,7 +18,7 @@ where no SMB options are required to be set:
 comment = CVE-2017-7494
 path = /tmp
 writable = yes
-browsable = yes
+browseable = yes
 guest ok = yes
 ```
 
diff --git a/documentation/modules/exploit/multi/http/magento_unserialize.md b/documentation/modules/exploit/multi/http/magento_unserialize.md
index 572e263f1a..43ad2331c2 100644
--- a/documentation/modules/exploit/multi/http/magento_unserialize.md
+++ b/documentation/modules/exploit/multi/http/magento_unserialize.md
@@ -68,7 +68,7 @@ If at some point the IP (base URL) of Magento has changed, then you will need to
 
 1. From the terminal, do: ```mysql -h localhost -u [username] -p[password]```
 2. In the SQL prompt, do: ```use [magento database name]```
-3. Do: ```select * from core_config_data;```, you should see both web/insecure/base_url (config ID 2) and web/secure/base_url (config ID 3) with the hardcoded IP.
+3. Do: ```select * from core_config_data;```, you should see both web/unsecure/base_url (config ID 2) and web/secure/base_url (config ID 3) with the hardcoded IP.
 4. Do: ```update core_config_data set value='http://[IP]/' where config_id=2;```
 5. Do: ```update core_config_data set value='https://[IP]/' where config_id=3;```
 6. Back to the Magento directory, do: ```sudo rm -rf var/cache/*```