zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

zip-guide.rst: clarify that an Abstract should not contain specification. 

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2019-09-03 14:19:44 +01:00
parent b25a4e6889
commit 0c7fcf636b
2 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
zip-guide.html
View File

@ -34,8 +34,9 @@ License: {usually MIT}</pre>
</section>
<section id="abstract">
<h2>Abstract</h2>
<p>{Describe what this proposal does, typically in a few paragraphs.}</p>
<p>{Use links where applicable, e.g. <a href="#protocol" id="id2" class="footnote_reference">2</a>.}</p>
<p>{Describe what this proposal does, typically in a few paragraphs.</p>
<p>The Abstract should only provide a summary of the ZIP; the ZIP should remain complete without the Abstract.</p>
<p>Use links where applicable, e.g. <a href="#protocol" id="id2" class="footnote_reference">2</a>.}</p>
</section>
<section id="motivation">
<h2>Motivation</h2>

7
zip-guide.rst
View File

@ -42,9 +42,12 @@ The terms below are to be interpreted as follows:
Abstract
========
{Describe what this proposal does, typically in a few paragraphs.}
{Describe what this proposal does, typically in a few paragraphs.
{Use links where applicable, e.g. [#protocol]_.}
The Abstract should only provide a summary of the ZIP; the ZIP should remain
complete without the Abstract.
Use links where applicable, e.g. [#protocol]_.}
Motivation