From dab5143f1ff69dde95c1a1cf42e98da835329d79 Mon Sep 17 00:00:00 2001
From: jdegand <70610011+jdegand@users.noreply.github.com>
Date: Sat, 16 Mar 2024 12:33:14 -0400
Subject: [PATCH] docs: bug-cd-md-revision-2

---
 docs/src/content/docs/challenges/angular/32-bug-cd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/content/docs/challenges/angular/32-bug-cd.md b/docs/src/content/docs/challenges/angular/32-bug-cd.md
index 313644c..6d5ebdb 100644
--- a/docs/src/content/docs/challenges/angular/32-bug-cd.md
+++ b/docs/src/content/docs/challenges/angular/32-bug-cd.md
@@ -26,7 +26,7 @@ In this small application, we have a navigation menu to route our application to
 The goal of the challenge is to debug this application and make it work.
 
 :::note
-Without knowing the exact reason for the issue, you can "fix" the error and get the program to function. One such approach would be to memoize the `getMenu` function. The application might work again, but make sure you really understand the problem and its consequences. Making it work isn't always enough; fixing this bug in the wrong way can cause a loss of performance or lead to other problems later on.  
+Without knowing the exact reason for the issue, you can "fix" the error and get the program to function. One such approach would be to memoize `getMenu`. The application might work again, but make sure you really understand the problem and its consequences. Making it work isn't always enough; fixing this bug in the wrong way can cause a loss of performance or lead to other problems later on.  
 :::
 
 ## Hints