From bb3a3b667759a9c5c72e490e0317afafa58d6308 Mon Sep 17 00:00:00 2001
From: Patrick Ohly <patrick.ohly@intel.com>
Date: Fri, 24 Jan 2025 12:26:56 +0100
Subject: [PATCH] KEP template: move guidance for line breaks

The last three new KEPs that I started to review all didn't use line-wrapping,
including one from an experienced Kubernetes contributor. Apparently we have
to put the existing guidance on line breaks into a more prominent spot.
---
 keps/NNNN-kep-template/README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/keps/NNNN-kep-template/README.md b/keps/NNNN-kep-template/README.md
index 7018679e98f..27c47182971 100644
--- a/keps/NNNN-kep-template/README.md
+++ b/keps/NNNN-kep-template/README.md
@@ -1,6 +1,13 @@
 <!--
 **Note:** When your KEP is complete, all of these comment blocks should be removed.
 
+Follow the guidelines of the [documentation style guide].
+In particular, wrap lines to a reasonable length, to make it
+easier for reviewers to cite specific portions, and to minimize diff churn on
+updates.
+
+[documentation style guide]: https://github.com/kubernetes/community/blob/master/contributors/guide/style-guide.md
+
 To get started with this template:
 
 - [ ] **Pick a hosting SIG.**
@@ -164,13 +171,6 @@ should help to ensure that the tone and content of the `Summary` section is
 useful for a wide audience.
 
 A good summary is probably at least a paragraph in length.
-
-Both in this section and below, follow the guidelines of the [documentation
-style guide]. In particular, wrap lines to a reasonable length, to make it
-easier for reviewers to cite specific portions, and to minimize diff churn on
-updates.
-
-[documentation style guide]: https://github.com/kubernetes/community/blob/master/contributors/guide/style-guide.md
 -->
 
 ## Motivation