Small TEP fixes 👼

TEP numbers, table of contents, comments.

Signed-off-by: Vincent Demeester <[email protected]>

teps/0003-tekton-catalog-organization.md

@@ -9,7 +9,7 @@ last-updated: 2020-07-07
 status: proposed
 ---
 
-# TEP-0002: Tekton Catalog Organization
+# TEP-0003: Tekton Catalog Organization
 
 <!-- toc -->
 - [Summary](#summary)
@@ -28,6 +28,7 @@ status: proposed
   - [Compatibility](#compatibility)
   - [Ownership](#ownership)
   - [Organization](#organization)
+    - [Example of a resource from catalog](#example-of-a-resource-from-catalog)
     - [Open questions](#open-questions-1)
   - [Requirements &amp; Guidelines](#requirements--guidelines)
   - [Deprecation &amp; Removal strategy](#deprecation--removal-strategy)
@@ -669,4 +670,4 @@ right away.  -->
 **To be completed** <!-- Use this section to detail wether this
 feature needs an upgrade or migration strategy. This is especially
 useful when we modify a behavior or add a feature that may replace and
-deprecate a current one.  -->
+deprecate a current one.  -->

teps/0004-task-results-in-final-tasks.md

@@ -8,7 +8,7 @@ last-updated: 2020-07-16
 status: implementable
 ---
 
-# TEP-NNNN: Task Results in Final Tasks
+# TEP-0004: Task Results in Final Tasks
 
 <!-- toc -->
 - [Summary](#summary)
@@ -306,6 +306,3 @@ validation failure if proj-name is not initialized.
 
 * https://github.com/tektoncd/pipeline/issues/2557
 * [Design Doc](https://docs.google.com/document/d/10iEJqVstY6k3KNvAXgffIJLcHRbPQ-GIAfQk5Dlrf3c/edit)
-
-
-

teps/0005-tekton-oci-bundles.md

@@ -1,41 +1,3 @@
-<!--
-**Note:** When your TEP is complete, all of these comment blocks should be removed.
-
-To get started with this template:
-
-- [ ] **Fill out this file as best you can.**
-  At minimum, you should fill in the "Summary", and "Motivation" sections.
-  These should be easy if you've preflighted the idea of the TEP with the
-  appropriate Working Group.
-- [ ] **Create a PR for this TEP.**
-  Assign it to people in the SIG that are sponsoring this process.
-- [ ] **Merge early and iterate.**
-  Avoid getting hung up on specific details and instead aim to get the goals of
-  the TEP clarified and merged quickly.  The best way to do this is to just
-  start with the high-level sections and fill out details incrementally in
-  subsequent PRs.
-
-Just because a TEP is merged does not mean it is complete or approved.  Any TEP
-marked as a `proposed` is a working document and subject to change.  You can
-denote sections that are under active debate as follows:
-
-```
-<<[UNRESOLVED optional short context or usernames ]>>
-Stuff that is being argued.
-<<[/UNRESOLVED]>>
-```
-
-When editing TEPS, aim for tightly-scoped, single-topic PRs to keep discussions
-focused.  If you disagree with what is already in a document, open a new PR
-with suggested changes.
-
-If there are new details that belong in the TEP, edit the TEP.  Once a
-feature has become "implemented", major changes should get new TEPs.
-
-The canonical place for the latest set of instructions (and the likely source
-of this file) is [here](/teps/NNNN-TEP-template/README.md).
-
--->
 # TEP-0005: Tekton OCI bundles
 
 <!-- toc -->