Fix OTEP template (open-telemetry#71)

RFCs were renamed to OTEPs quite a while ago

0000-template.md

@@ -1,4 +1,4 @@
-# Replace this with your awesome RFC title
+# Replace this with your awesome OTEP title
 
 Short (one sentence) summary, e.g., something that would be appropriate for a [CHANGELOG](https://keepachangelog.com/) or release notes.
 
@@ -20,21 +20,21 @@ From a technical perspective, how do you propose accomplishing the proposal? In
 * Likely error modes (and how to handle them)
 * Corner cases (and how to handle them)
 
-While you do not need to prescribe a particular implementation - indeed, RFCs should be about **behaviour**, not implementation! - it may be useful to provide at least one suggestion as to how the proposal *could* be implemented. This helps reassure reviewers that implementation is at least possible, and often helps them inspire them to think more deeply about trade-offs, alternatives, etc.
+While you do not need to prescribe a particular implementation - indeed, OTEPs should be about **behaviour**, not implementation! - it may be useful to provide at least one suggestion as to how the proposal *could* be implemented. This helps reassure reviewers that implementation is at least possible, and often helps them inspire them to think more deeply about trade-offs, alternatives, etc.
 
 ## Trade-offs and mitigations
 
 What are some (known!) drawbacks? What are some ways that they might be mitigated?
 
-Note that mitigations do not need to be complete *solutions*, and that they do not need to be accomplished directly through your proposal. A suggested mitigation may even warrant its own RFC!
+Note that mitigations do not need to be complete *solutions*, and that they do not need to be accomplished directly through your proposal. A suggested mitigation may even warrant its own OTEP!
 
 ## Prior art and alternatives
 
 What are some prior and/or alternative approaches? For instance, is there a corresponding feature in OpenTracing or OpenCensus? What are some ideas that you have rejected?
 
 ## Open questions
 
-What are some questions that you know aren't resolved yet by the RFC? These may be questions that could be answered through further discussion, implementation experiments, or anything else that the future may bring.
+What are some questions that you know aren't resolved yet by the OTEP? These may be questions that could be answered through further discussion, implementation experiments, or anything else that the future may bring.
 
 ## Future possibilities