Fix line length

NO_CHANGELOG=changelog
NO_DOC=changelog
NO_TEST=changelog

changelogs/unreleased/gh-3211-per-module-log_level.md

@@ -3,5 +3,5 @@
 * **[Breaking change]** Now the log message contains the name of a module from
   which the logging function was called (gh-3211).
 
-* Now the log level can be set for specific modules using `log.cfg{modules = {...}}` or
-  `box.cfg{log_modules = {...}}` (gh-3211).
+* Now the log level can be set for specific modules using `log.cfg{modules = {...}}`
+  or `box.cfg{log_modules = {...}}` (gh-3211).

changelogs/unreleased/gh-6650-round-with-big-precision.md

 ## bugfix/sql
 
-* Now the `ROUND()` functions works correctly on arguments with big precision (gh-6650).
+* Now the `ROUND()` functions works correctly on arguments with big precision
+ (gh-6650).

changelogs/unreleased/gh-6832-httpc-params-encoding.md

 ## feature/lua/http client
 
 * Added a new option `params` to add query parameters to URI using a Lua table.
-  These parameters are encoded to a query string and passed to the HTTP request (gh-6832).
+  These parameters are encoded to a query string and passed to the HTTP request
+  (gh-6832).

changelogs/unreleased/gh-6833-decode-body-http-response.md

 ## feature/lua/http client
 
 * Added a new method `response:decode()`. It decodes an HTTP response body to
-  a Lua object. The decoding result depends on the response content type. The following
-  content types are supported by default: `application/json`, `application/yaml`,
-  `application/msgpack`. Users can define decoding rules for other content types
-  by writing their own decoding functions. (gh-6833).
+  a Lua object. The decoding result depends on the response content type. The
+  following content types are supported by default: `application/json`,
+  `application/yaml`, `application/msgpack`. Users can define decoding rules for
+  other content types by writing their own decoding functions (gh-6833).

changelogs/unreleased/gh-6833-encode-body-http-request.md

 ## feature/lua/http client
 
-* Now the HTTP client is able to encode Lua objects automatically when it is possible.
-  The encoding format depends on the request content type. The following
-  content types are supported by default: `application/json`, `application/yaml`,
-  `application/msgpack`. Users can define encoding rules for other content types
-  by writing their own encoding functions. (gh-6833).
+* Now the HTTP client is able to encode Lua objects automatically when it is
+  possible. The encoding format depends on the request content type.
+  The following content types are supported by default: `application/json`,
+  `application/yaml`, `application/msgpack`. Users can define encoding rules
+  for other content types by writing their own encoding functions (gh-6833).