Small update to from "launched and promoted" to "merged"

Author: ematejska

rfcs/yyyymmdd-rfc-template.md

@@ -65,7 +65,7 @@ Make sure you’ve thought through and addressed the following sections. If a se
     - The minimum requirements for this are to consider how this would be used in a Keras-based workflow, as well as a non-Keras (low-level) workflow. If either isn’t applicable, explain why.
     - It should show the usage of the new feature in an end to end example (from data reading to serving, if applicable). Many new features have unexpected effects in parts far away from the place of change that can be found by running through an end-to-end example. TFX [Examples](https://github.com/tensorflow/tfx/tree/master/tfx/examples) have historically been good in identifying such unexpected side-effects and are as such one recommended path for testing things end-to-end.
     - This should be written as if it is documentation of the new feature, i.e., consumable by a user, not a TensorFlow developer. 
-    - The code does not need to work (since the feature is not implemented yet) but the expectation is that the code does work before the feature can be launched or promoted. 
+    - The code does not need to work (since the feature is not implemented yet) but the expectation is that the code does work before the feature can be merged. 
 
 ### Compatibility
 * Does the design conform to the backwards & forwards compatibility [requirements](https://www.tensorflow.org/programmers_guide/version_compat)?