From e4c384fa7d6b42e7cc968d4926f3ca07636a8747 Mon Sep 17 00:00:00 2001
From: lena-larionova <54370747+lena-larionova@users.noreply.github.com>
Date: Fri, 15 Sep 2023 10:10:30 -0700
Subject: [PATCH] line breaks and add "render" to short desc

---
 cmd/file_render.go | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/cmd/file_render.go b/cmd/file_render.go
index 72799bf5d..567e820dc 100644
--- a/cmd/file_render.go
+++ b/cmd/file_render.go
@@ -27,14 +27,17 @@ func executeFileRenderCmd(_ *cobra.Command, _ []string) error {
 func newFileRenderCmd() *cobra.Command {
 	renderCmd := &cobra.Command{
 		Use:   "render",
-		Short: "Combines multiple complete configuration files into one Kong declarative config file.",
-		Long:  `Combines multiple complete configuration files into one Kong
+		Short: "Combines multiple complete configuration files and renders them as one Kong declarative config file.",
+		Long:  `Combines multiple complete configuration files and renders them as one Kong
 	declarative config file.
 
- This command renders a full declarative configuration in JSON or YAML format by assembling multiple files and populating defaults and environment substitutions. This command is useful to observe what configuration would be sent prior to synchronizing to the gateway.
+ This command renders a full declarative configuration in JSON or YAML format by assembling 
+ multiple files and populating defaults and environment substitutions. 
+ This command is useful to observe what configuration would be sent prior to synchronizing to 
+ the gateway.
  
-In comparison to the "deck file merge" command, the render command accepts complete configuration files, 
- while "deck file merge" can operate on partial files.
+ In comparison to the "deck file merge" command, the render command accepts 
+ complete configuration files, while "deck file merge" can operate on partial files.
 
  For example, the following command takes two input files and renders them as one 
  combined JSON file: