diff --git a/guides/proposal.rst b/guides/proposal.rst index d746813b828d16390ef6dcfd9d352b5e3e55477a..1f9b5e5d7a376b7d91e1813f168eebded4d3e364 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>`_.