From 79a1178b8848f97c416b39e316cb26ae7228e338 Mon Sep 17 00:00:00 2001
From: Lauren Camacci <55750466+lcamacci@users.noreply.github.com>
Date: Tue, 2 Jun 2020 09:35:26 -0400
Subject: [PATCH] Update setup-templates.md

---
 BuildMaster/applications/concepts/setup-templates.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/BuildMaster/applications/concepts/setup-templates.md b/BuildMaster/applications/concepts/setup-templates.md
index c810a86c..99267da8 100644
--- a/BuildMaster/applications/concepts/setup-templates.md
+++ b/BuildMaster/applications/concepts/setup-templates.md
@@ -58,7 +58,7 @@ Plan settings may also require a `RequiresEdit` property, which indicates the pl
 #### Renaming Templates
 Although you can't rename a setup template once you've created it, you can duplicate it, adding the new name, and delete the old template.
 
-### Importing and Exporting Setup Templates{#importing-exporting data-title="Important and Exporting"}
+### Importing and Exporting Setup Templates{#importing-exporting data-title="Importing and Exporting"}
 To make application setup templates work transparently with application template packages, BuildMaster behaves as follows:
 
 * When you export your application as a template, the associated setup template will automatically be bundled in export package