diff --git a/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java b/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
index b74f05e90..5452aa209 100644
--- a/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
+++ b/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
@@ -27,8 +27,8 @@ import org.owasp.dependencycheck.dependency.Dependency;
 /**
  * This analyzer accepts the fully resolved .gemspec created by the Ruby bundler (http://bundler.io)
  * for better evidence results. It also tries to resolve the dependency packagePath 
- * to where the gem is actually installed. Then during <code>AnalysisPhase.PRE_FINDING_ANALYSIS</code>
- * <code>DependencyBundlingAnalyzer</code> would merge two .gemspec dependencies together if 
+ * to where the gem is actually installed. Then during {@link AnalysisPhase.PRE_FINDING_ANALYSIS}
+ * {@link DependencyBundlingAnalyzer} will merge two .gemspec dependencies together if 
  * <code>Dependency.getPackagePath()</code> are the same.
  * 
  * Ruby bundler creates new .gemspec files under a folder called "specifications" at deploy time, 
@@ -37,8 +37,8 @@ import org.owasp.dependencycheck.dependency.Dependency;
  * evidences, whereas the original .gemspec from source often contain variables for attributes
  * that can't be used for evidences.
  * 
- * Note this analyzer share the same <code>Settings.KEYS.ANALYZER_RUBY_GEMSPEC_ENABLED</code> as
- * <code>RubyGemspecAnalyzer</code>, so it will enabled/disabled with <code>RubyGemspecAnalyzer</code>.
+ * Note this analyzer share the same {@link Settings.KEYS.ANALYZER_RUBY_GEMSPEC_ENABLED} as
+ * {@link RubyGemspecAnalyzer}, so it will enabled/disabled with {@link RubyGemspecAnalyzer}.
  *
  * @author Bianca Jiang (biancajiang@gmail.com)
  */