From a1fc01d39b9fa7d900abd8a3cf155929a0b236e9 Mon Sep 17 00:00:00 2001
From: Teresa Allen <teresa.allen@salesforce.com>
Date: Thu, 24 Aug 2023 12:22:41 -0400
Subject: [PATCH] Update rules.md

---
 docs/_articles/en/v3.x/salesforce-graph-engine/rules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/_articles/en/v3.x/salesforce-graph-engine/rules.md b/docs/_articles/en/v3.x/salesforce-graph-engine/rules.md
index dd9603df6..febf14c39 100644
--- a/docs/_articles/en/v3.x/salesforce-graph-engine/rules.md
+++ b/docs/_articles/en/v3.x/salesforce-graph-engine/rules.md
@@ -411,7 +411,7 @@ This warning is thrown when a database operation occurs in a class that has no e
 
 ## Pilot Rules
 
-### PerformNullCheckOnSoqlVariables#
+### PerformNullCheckOnSoqlVariables <a name='PerformNullCheckOnSoqlVariables'>#</a>
 
 PerformNullCheckOnSoqlVariables identifies SOQL queries with variables in WHERE clauses that lack null checks. 
 SOQL queries with variables on WHERE clauses become expensive when the variable value is unintentionally null. When the variable value is null, an O(1) operation turns into an O(n) operation. The entire table is scanned, but returns no results.