From be89fcf577d04a9570ca557dec217529910a90a1 Mon Sep 17 00:00:00 2001
From: BekahHW <34313413+BekahHW@users.noreply.github.com>
Date: Thu, 16 Nov 2023 11:53:29 -0500
Subject: [PATCH] Update docs/maintainers/maintainers-guide.md

Co-authored-by: Ayu Adiati <45172775+adiati98@users.noreply.github.com>
---
 docs/maintainers/maintainers-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/maintainers/maintainers-guide.md b/docs/maintainers/maintainers-guide.md
index a69b5b2d..f90f7a92 100644
--- a/docs/maintainers/maintainers-guide.md
+++ b/docs/maintainers/maintainers-guide.md
@@ -159,7 +159,7 @@ Finally, it's time to add the details of your highlight. You can add a descripti
 
 Writing an effective highlight is key to attracting contributors to your project. Here are some tips to help you write an effective highlight:
 
-#### Issues
+#### Highlighting Issues
 
 1. **Focus on the Problem Solved**: Begin by briefly describing the problem or challenge the issue addresses. This sets the context for why it was important.
 2. **Acknowledge Contributor(s)**: Mention the contributor(s) who reported or worked on the issue, recognizing their effort.