From e793cc4a1e1d8738bba72bab37120bfb64eca9af Mon Sep 17 00:00:00 2001
From: Caitlin Lamprecht <42557454+MagicWishbone6@users.noreply.github.com>
Date: Fri, 26 Jan 2024 14:59:50 -0600
Subject: [PATCH] Updated Apex Type Names tables

The two tables in the Naming Conventions document under the section about Apex Type Names were not showing as intended. This update corrects them.
---
 _pages/Salesforce-Naming-Conventions.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/_pages/Salesforce-Naming-Conventions.md b/_pages/Salesforce-Naming-Conventions.md
index 76c87a6..e9758d7 100644
--- a/_pages/Salesforce-Naming-Conventions.md
+++ b/_pages/Salesforce-Naming-Conventions.md
@@ -481,14 +481,15 @@ The following are examples of Apex type naming that should not be used
 
 Type Name | Reason 
 -----------|:------
-map Contacts | "map", “id”, and “string” do not start with an uppercase letter. 
-String Contact | “string” does not start with an uppercase letter. 
+map Contacts | "map" does not start with an uppercase letter 
+string Contact | “string” does not start with an uppercase letter 
 
 The following are examples of the naming convention that will be used 
 
 Type Name | Reason 
 -----------|:------
-Map Contacts | Starts with an uppercase letter String Contact Starts with an uppercase letter
+Map Contacts | Starts with an uppercase letter
+String Contact | Starts with an uppercase letter
 
 ____