Browse Source

Fix: typos & urls in PIP

Herman Schoenfeld 8 years ago
parent
commit
00e39e0c4d
2 changed files with 6 additions and 6 deletions
  1. 4 4
      PIP/PIP-0001.md
  2. 2 2
      PIP/README.md

+ 4 - 4
PIP/PIP-0001.md

@@ -1,5 +1,5 @@
 <pre>
 <pre>
-  BIP: 1
+  PIP: 1
   Title: PIP Purpose and Guidelines
   Title: PIP Purpose and Guidelines
   Type: Process
   Type: Process
   Impact: None
   Impact: None
@@ -18,7 +18,7 @@ PIPs are intended to be the primary mechanisms for proposing new features and do
 
 
 ## Copyright
 ## Copyright
 
 
-This BIP is dual-licensed under the Open Publication License and BSD 2-clause license.
+This PIP is dual-licensed under the Open Publication License and BSD 2-clause license.
 
 
 
 
 ## PIP Workflow
 ## PIP Workflow
@@ -50,7 +50,7 @@ A PIP submission should be written in mark-down (GitHub flavor) and consist of t
  - <b>Specification</b> -- Full technical description of the proposed new feature, clear enough for i
  - <b>Specification</b> -- Full technical description of the proposed new feature, clear enough for i
  - <b>Rationale</b> -- Discussion why was the specification was chosen over alternate designs. Evidence supporting the specification should be provided here, as well as community concerns and consensus.
  - <b>Rationale</b> -- Discussion why was the specification was chosen over alternate designs. Evidence supporting the specification should be provided here, as well as community concerns and consensus.
  - <b>Backwards Compatibility</b> -- Any backwards incompatibilities should be described here, as well as work-arounds/solutions for these incompatibilities.
  - <b>Backwards Compatibility</b> -- Any backwards incompatibilities should be described here, as well as work-arounds/solutions for these incompatibilities.
- - <b>Reference Implementation</b> -- The reference implementation must be provided before BIP is Completed.
+ - <b>Reference Implementation</b> -- The reference implementation must be provided before PIP is Completed.
  - <b>Links</b> -- references and links to relevant material
  - <b>Links</b> -- references and links to relevant material
 
 
 PIP editors can use [this online editor](https://jbt.github.io/markdown-editor/) for editing and/or previewing their PIP submission.
 PIP editors can use [this online editor](https://jbt.github.io/markdown-editor/) for editing and/or previewing their PIP submission.
@@ -59,7 +59,7 @@ PIP editors can use [this online editor](https://jbt.github.io/markdown-editor/)
 
 
 <pre>
 <pre>
   PIP: &lt;<i>PIP number, or "?" before being assigned</i>&gt;
   PIP: &lt;<i>PIP number, or "?" before being assigned</i>&gt;
-  Title: &lt;<i>BIP title; maximum 44 characters</i>&gt;
+  Title: &lt;<i>PIP title; maximum 44 characters</i>&gt;
   Type &lt;<i>The type of PIP, see below for options</i>&gt;
   Type &lt;<i>The type of PIP, see below for options</i>&gt;
   Author: &lt;<i>list of authors' real names and email addrs</i>&gt;
   Author: &lt;<i>list of authors' real names and email addrs</i>&gt;
   Impact &lt;<i>How impactful the proposed changes are, see below for details.</i>&gt;
   Impact &lt;<i>How impactful the proposed changes are, see below for details.</i>&gt;

+ 2 - 2
PIP/README.md

@@ -1,7 +1,7 @@
 # PascalCoin Improvement Proposals (PIP)
 # PascalCoin Improvement Proposals (PIP)
 
 
-People wishing to submit PIPs, first should discuss their idea on the [PascalCoin Slack](pascalcoin.org/slack-self-invite). 
-If they wish to continue, edit your PIP in accordance to the standard [standard](PIP-00001.md) and submit to the PIP Maintainer for publication here.
+People wishing to submit PIPs, first should discuss their idea on the [PascalCoin Slack](http://pascalcoin.org/slack-self-invite/). 
+If they wish to continue, edit your PIP in accordance to the standard [standard](PIP-0001.md) and submit to the PIP Maintainer for publication here.
 
 
 ## All PIPs
 ## All PIPs