From 5ed192e5830a21b08402f462f526b9493efaa9cd Mon Sep 17 00:00:00 2001
From: Deepak Khatri <deepaklorkhatri7@gmail.com>
Date: Thu, 8 Feb 2024 18:50:58 +0530
Subject: [PATCH] Remove redundant text

---
 guides/proposal.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guides/proposal.rst b/guides/proposal.rst
index d746813..1f9b5e5 100644
--- a/guides/proposal.rst
+++ b/guides/proposal.rst
@@ -13,7 +13,7 @@ How to write a successful proposal
 ***********************************
 
 `BeagleBoard.org <https://www.beagleboard.org/>`_ has received a large number of GSoC student proposals over the years 
-that we have participated in the program. Some of these proposals are quite good, but many are poor proposals that would 
+that we have participated. Some of these proposals are quite good, but many are poor proposals that would 
 not be accepted by any organization participating in GSoC. Unsuccessful proposals often do/have the following:
 
 1. Try to pass off previous school projects as something to do for GSoC. The work has already done, and the project often has very little to do with `BeagleBoard.org hardware <https://www.beagleboard.org/boards>`_.
-- 
GitLab