From 372c3614a958c3d5026d535c7f23a177b3da4b09 Mon Sep 17 00:00:00 2001
From: Antoni Ivanov <aivanov@vmware.com>
Date: Fri, 28 Jul 2023 16:40:12 +0300
Subject: [PATCH 1/2] specs: try to make it clear what deliverables should be

Improving VEP recommendations to make sure we include expected deliverables as part of the VEP
---
 specs/NNNN-template/README.md | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/specs/NNNN-template/README.md b/specs/NNNN-template/README.md
index d6c3b79bcc..58d54542aa 100644
--- a/specs/NNNN-template/README.md
+++ b/specs/NNNN-template/README.md
@@ -57,9 +57,13 @@ Explain the user problem that need to be solved.
 
 ## Requirements and goals
 <!--
-It tells **what** is it trying to achieve?
-List the specific goals (functional and nonfunctional requirements)? How will we
-know that this has succeeded?
+It tells **what** is it trying to achieve including expected deliverables.
+List the specific goals (functional and nonfunctional requirements)? 
+It's recommended to specify metrics that can be used to check the goal has been achieved. 
+
+Specify for what type of users, what is going to be delivered. 
+Recommended (but not required format) is 
+User <persona/type of user>, they need <new deliverable/feature/improvement>, so that <reason> 
 
 Specify non-goals. Clearly, the list of non-goals can't be exhaustive.
 Non-goals are only features, which a contributor can reasonably assume were a goal.
@@ -149,9 +153,10 @@ Consider at least the below topics but you do not need to cover those that are n
 -->
 
 
-## Implementation stories
+## Implementation stories  
 <!--
-Optionally, describe what are the implementation stories (eventually we'd create github issues out of them).
+Optionally, describe what are the implementation stories. Link to Milestone or initiative in Github is fine
+As part of the implementation make sure to include stories covering release/launch plan, promotional activities before the release, 
 -->
 
 ## Alternatives

From 470b8f0b2af26dbee08c0719b3d5292cadf52424 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Fri, 28 Jul 2023 13:43:54 +0000
Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 specs/NNNN-template/README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/specs/NNNN-template/README.md b/specs/NNNN-template/README.md
index 58d54542aa..dd52f8546c 100644
--- a/specs/NNNN-template/README.md
+++ b/specs/NNNN-template/README.md
@@ -58,12 +58,12 @@ Explain the user problem that need to be solved.
 ## Requirements and goals
 <!--
 It tells **what** is it trying to achieve including expected deliverables.
-List the specific goals (functional and nonfunctional requirements)? 
-It's recommended to specify metrics that can be used to check the goal has been achieved. 
+List the specific goals (functional and nonfunctional requirements)?
+It's recommended to specify metrics that can be used to check the goal has been achieved.
 
-Specify for what type of users, what is going to be delivered. 
-Recommended (but not required format) is 
-User <persona/type of user>, they need <new deliverable/feature/improvement>, so that <reason> 
+Specify for what type of users, what is going to be delivered.
+Recommended (but not required format) is
+User <persona/type of user>, they need <new deliverable/feature/improvement>, so that <reason>
 
 Specify non-goals. Clearly, the list of non-goals can't be exhaustive.
 Non-goals are only features, which a contributor can reasonably assume were a goal.
@@ -153,10 +153,10 @@ Consider at least the below topics but you do not need to cover those that are n
 -->
 
 
-## Implementation stories  
+## Implementation stories
 <!--
 Optionally, describe what are the implementation stories. Link to Milestone or initiative in Github is fine
-As part of the implementation make sure to include stories covering release/launch plan, promotional activities before the release, 
+As part of the implementation make sure to include stories covering release/launch plan, promotional activities before the release,
 -->
 
 ## Alternatives