From dfd423e5e297019cca8afb11252a2f40ff8c0de7 Mon Sep 17 00:00:00 2001
From: "P. L. Lim" <2090236+pllim@users.noreply.github.com>
Date: Tue, 19 Nov 2024 15:57:27 -0500
Subject: [PATCH] Fix typos as pointed out by KavyaKolavasi1

---
 contribute.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/contribute.html b/contribute.html
index 23295b5..9c6daa7 100755
--- a/contribute.html
+++ b/contribute.html
@@ -180,7 +180,7 @@ <h2 id="formal-project-role">Taking on a formal project role<a class="paralink"
             For example, being a core sub-package maintainer involves interacting with users and
             responding to bug reports in a timely manner. If you are interested in taking on such a role, you can volunteer
             either on <a href="http://groups.google.com/group/astropy-dev">astropy-dev</a>, by talking to a holder of the
-  role you are interested in, or a coordination commitee member.
+  role you are interested in, or a coordination committee member.
         </p>
 
   </section>
@@ -208,7 +208,7 @@ <h2 id="justify-contribution">For academics: How to justify your contribution<a
     <p> While in some more technical areas, contributing code is recognized as a
       goal in and of itself, some academic fields have not yet developed a clear
       understanding of the role of code development relative to other more
-      traditional contributions like publication. This sections aims to
+      traditional contributions like publication. This section aims to
       provide suggestions to academics for how you might justify contributions
       to the Astropy project if you are in a field or institution that needs
       convincing of the value of such contributions.