Clarify template instructions

Author: david-christiansen

proposals/templates/CommunityProject.md

@@ -1,47 +1,51 @@
 # Community Project Template - place your title here
 
-This template is for Haskell Foundation Technical Proposals that are community projects asking for support.
-Community project proposals are requests that the Haskell Foundation allocate funding to a particular project or goal to be executed by community members.
+_This template is for Haskell Foundation Technical Proposals that are community projects asking for support.
+Community project proposals are requests that the Haskell Foundation allocate funding to a particular project or goal to be executed by community members._
+
+_Please delete the italic text before submitting._
+
 
 ## Abstract
 
-This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution.
+_This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution._
 
 ## Background
 
-This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level overview of the technical details and some history).
+_This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level overview of the technical details and some history)._
 
 ## Problem Statement
 
-This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
-It should also enumerate the requirements against which a solution should be evaluated.
+_This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
+It should also enumerate the requirements against which a solution should be evaluated._
 
 ## Prior Art and Related Efforts
 
-This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing to address the problem.
+_This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing to address the problem.
 It should describe the relationship between the proposed work and the existing efforts.
-If past attempts did not succeed, this section should provide a theory of why not.
+If past attempts did not succeed, this section should provide a theory of why not._
 
 ## Technical Content
 
-This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future). 
+_This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future). 
 It should also describe the benefits, drawbacks, and risks that are associated with these decisions.
-It can be a good idea to describe alternative approaches here as well, and why the proposer prefers the current approach.
+It can be a good idea to describe alternative approaches here as well, and why the proposer prefers the current approach._
 
 ## Timeline
 
-When will the project be completed?
-What are the intermediate steps and intermediate concrete deliverables for the community?
+_When will the project be completed?
+What are the intermediate steps and intermediate concrete deliverables for the community?_
 
 ## Budget
 
-How much money is needed to accomplish the goal? How will it be used?
+_How much money is needed to accomplish the goal?
+How will it be used?_
 
 ## Stakeholders
 
-Who stands to gain or lose from the implementation of this proposal?
-Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups.
+_Who stands to gain or lose from the implementation of this proposal?
+Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups._
 
 ## Success
 
-Under what conditions will the project be considered a success?
+_Under what conditions will the project be considered a success?_

proposals/templates/HFProject.md

@@ -1,49 +1,49 @@
 # Haskell Foundation Project Template - place your title here
 
-This template is for Haskell Foundation Technical Proposals that are projects to be executed by the Haskell Foundation, without necessarily
-having any further involvement by the proposer.
+_This template is for Haskell Foundation Technical Proposals that are projects to be executed by the Haskell Foundation, without necessarily having any further involvement by the proposer._
 
+_Please delete the italic text before submitting._
 
 ## Abstract
 
-This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution.
+_This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution._
 
 ## Background
 
-This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level overview of the technical details and some history).
+_This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level overview of the technical details and some history)._
 
 ## Problem Statement
 
-This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
-It should also enumerate the requirements against which a solution should be evaluated.
+_This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
+It should also enumerate the requirements against which a solution should be evaluated._
 
 ## Prior Art and Related Efforts
 
-This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing to address the problem.
+_This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing to address the problem.
 It should describe the relationship between the proposed work and the existing efforts.
-If past attempts did not succeed, this section should provide a theory of why not.
+If past attempts did not succeed, this section should provide a theory of why not._
 
 ## Technical Content
 
-This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future).
+_This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future).
 It should also describe the benefits, drawbacks, and risks that are associated with these decisions.
-It can be a good idea to describe alternative approaches here as well, and why the proposer prefers the current approach.
+It can be a good idea to describe alternative approaches here as well, and why the proposer prefers the current approach._
 
 ## Timeline
 
-Are there any deadlines that the HF needs to be aware of?
+_Are there any deadlines that the HF needs to be aware of?_
 
 ## Budget
 
-How much money is needed to accomplish the goal?
-How will it be used?
+_How much money is needed to accomplish the goal?
+How will it be used?_
 
 ## Stakeholders
 
-Who stands to gain or lose from the implementation of this proposal?
-Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups.
+_Who stands to gain or lose from the implementation of this proposal?
+Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups._
 
 ## Success
 
-Under what conditions will the project be considered a success?
+_Under what conditions will the project be considered a success?_
 

proposals/templates/RFC.md

@@ -1,39 +1,39 @@
 # RFC Template - place your title here
 
-This template is for Haskell Foundation Technical Proposals that have the character of a request for comment (RFC).
+_This template is for Haskell Foundation Technical Proposals that have the character of a request for comment (RFC).
 An RFC is a project with importance to the broad Haskell community that the proposer intends to execute themselves, using their own resources.
-The proposer is seeking feedback from the community to help make the project a success.
+The proposer is seeking feedback from the community to help make the project a success._
+
+_Please delete the italic text before submitting._
 
 ## Abstract
 
-This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution.
+_This section should provide a summary of the proposal that identifies the key problems to be solved and summarizes the solution._
 
 ## Background
 
-This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level
-overview of the technical details and some history).
+_This section should explain any background (targeting a casual audience) needed to understand the proposal’s motivation (e.g. a high level overview of the technical details and some history)._
 
 ## Problem Statement
 
-This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
-It should also enumerate the requirements against which a solution should be evaluated.
+_This section should describe the problem that the proposal intends to solve and how solving the problem will benefit the Haskell community.
+It should also enumerate the requirements against which a solution should be evaluated._
 
 ## Prior Art and Related Efforts
 
-This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing
-to address the problem. It should describe the relationship between the proposed work and the existing efforts.
-If past attempts did not succeed, this section should provide a theory of why not.
+_This section should describe prior attempts to solve the problem, other relevant prior work, and what others in the community are doing to address the problem. It should describe the relationship between the proposed work and the existing efforts.
+If past attempts did not succeed, this section should provide a theory of why not._
 
 ## Technical Content
 
-This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future). 
-It should also describe the benefits, drawbacks, and risks that are associated with these decisions.
+_This section should describe the work that is being proposed to the community for comment, including both technical aspects (choices of system architecture, integration with existing tools and workflows) and community governance (how the developed project will be administered, maintained, and otherwise cared for in the future). 
+It should also describe the benefits, drawbacks, and risks that are associated with these decisions._
 
 ## Stakeholders
 
-Who stands to gain or lose from the implementation of this proposal?
-Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups.
+_Who stands to gain or lose from the implementation of this proposal?
+Proposals should identify stakeholders so that they can be contacted for input, and a final decision should not occur without having made a good-faith effort to solicit representative feedback from important stakeholder groups._
 
 ## Success
 
-When will the project be considered a success? How long is it expected to take?
+_When will the project be considered a success? How long is it expected to take?_