From 73e7edf06d43f710e460eb318677b88a6bc858e9 Mon Sep 17 00:00:00 2001
From: Yoriyasu Yano <430092+yorinasub17@users.noreply.github.com>
Date: Wed, 26 Feb 2020 16:42:41 -0800
Subject: [PATCH] [skip ci] fix more broken links

---
 _docs/rfc/imports.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_docs/rfc/imports.md b/_docs/rfc/imports.md
index dddc29b8b5..6f508a2d50 100644
--- a/_docs/rfc/imports.md
+++ b/_docs/rfc/imports.md
@@ -104,7 +104,7 @@ expensive solutions. The following is a summary of the solutions to be built:
 
 - [Short term: read_terragrunt_config helper function](#read_terragrunt_config-helper-function)
 - [Medium term: import blocks](#import-blocks)
-- [Long term: single terragrunt.hcl file](#single-terragrunt-hcl-file-per-environment)
+- [Long term: single terragrunt.hcl file](#single-terragrunthcl-file-per-environment)
 
 ### read_terragrunt_config helper function
 
@@ -272,7 +272,7 @@ Cons:
 Let's take a look at a few common use cases and how we might use `import` to address them:
 
 - [Hierarchical variables included across multiple terragrunt.hcl
-  files](#import-block-hierarchical-variables-included-across-multiple-terragrunt-hcl-files)
+  files](#import-block-hierarchical-variables-included-across-multiple-terragrunthcl-files)
 - [Reusing common variables](#import-block-reusing-common-variables)
 - [Reusing dependencies](#import-block-reusing-dependencies)
 - [Keeping remote state configuration DRY](#import-block-keeping-remote-state-configuration-dry)