From 7924344a4544f6a8a8a6c8454ae14bbe47df9339 Mon Sep 17 00:00:00 2001
From: sinn3r <wei_chen@rapid7.com>
Date: Thu, 5 Dec 2013 16:22:46 -0800
Subject: [PATCH] Updated Common Metasploit Module Coding Mistakes (markdown)

---
 Common-Metasploit-Module-Coding-Mistakes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Common-Metasploit-Module-Coding-Mistakes.md b/Common-Metasploit-Module-Coding-Mistakes.md
index 75e912847d..926ae1d5a4 100644
--- a/Common-Metasploit-Module-Coding-Mistakes.md
+++ b/Common-Metasploit-Module-Coding-Mistakes.md
@@ -2,7 +2,7 @@ This is a collection of all the bad code we often see in Metasploit modules.  Yo
 
 Note: Some of these examples use puts() for demo purposes, but you should always use print_status / print_error when writing a module.
 
-### Examples:
+### Bad Examples You Shouldn't Follow:
 
 1. Not checking the return value of a Metasploit API
 2. Ruby 1.9.3 vs 1.8.7... gotcha!