From baa691021c0c61278c7c700f9d349b52aeef17b8 Mon Sep 17 00:00:00 2001
From: Pavel Semyonov <p.semyonov@vk.team>
Date: Mon, 16 Jan 2023 13:19:54 +0700
Subject: [PATCH] Proofread changelogs
Fix grammar, wording, and formatting
NO_CHANGELOG=changelog
NO_DOC=changelog
NO_TEST=changelog
---
.../unreleased/gh-6650-round-with-big-precision.md | 2 +-
.../unreleased/gh-6793-datetime-set-with-tzoffset.md | 4 ++--
changelogs/unreleased/gh-6832-httpc-params-encoding.md | 4 ++--
changelogs/unreleased/gh-6832-uri-values.md | 4 ++--
.../unreleased/gh-6833-decode-body-http-response.md | 10 +++++-----
.../unreleased/gh-6833-encode-body-http-request.md | 9 +++++----
6 files changed, 17 insertions(+), 16 deletions(-)
diff --git a/changelogs/unreleased/gh-6650-round-with-big-precision.md b/changelogs/unreleased/gh-6650-round-with-big-precision.md
index 20328e3891..75eb1fb198 100644
--- a/changelogs/unreleased/gh-6650-round-with-big-precision.md
+++ b/changelogs/unreleased/gh-6650-round-with-big-precision.md
@@ -1,3 +1,3 @@
## bugfix/sql
-* Now ROUND() with big precision works properly (gh-6650).
+* Now the `ROUND()` functions works correctly on arguments with big precision (gh-6650).
diff --git a/changelogs/unreleased/gh-6793-datetime-set-with-tzoffset.md b/changelogs/unreleased/gh-6793-datetime-set-with-tzoffset.md
index 56d7868b8c..44e6c1ce88 100644
--- a/changelogs/unreleased/gh-6793-datetime-set-with-tzoffset.md
+++ b/changelogs/unreleased/gh-6793-datetime-set-with-tzoffset.md
@@ -1,5 +1,5 @@
## bugfix/datetime
-* Fixed a bug in datetime module when `date:set{tzoffset=XXX}` did not
- produce the same result with `date.new{tzoffset=XXX}` for the same
+* Fixed a bug in the datetime module when `date:set{tzoffset=XXX}` did
+ not produce the same result with `date.new{tzoffset=XXX}` for the same
set of attributes passed (gh-6793).
diff --git a/changelogs/unreleased/gh-6832-httpc-params-encoding.md b/changelogs/unreleased/gh-6832-httpc-params-encoding.md
index 10f731ab51..6269320dff 100644
--- a/changelogs/unreleased/gh-6832-httpc-params-encoding.md
+++ b/changelogs/unreleased/gh-6832-httpc-params-encoding.md
@@ -1,4 +1,4 @@
## feature/lua/http client
-* Added a new option to add query parameters into URI using a Lua table. These
- parameters are encoded to a query string and passed to HTTP request (gh-6832).
+* 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).
diff --git a/changelogs/unreleased/gh-6832-uri-values.md b/changelogs/unreleased/gh-6832-uri-values.md
index 2a1af67067..57bfcf8652 100644
--- a/changelogs/unreleased/gh-6832-uri-values.md
+++ b/changelogs/unreleased/gh-6832-uri-values.md
@@ -1,9 +1,9 @@
## feature/lua/uri
-* Add method `uri.values()` that allows a user to represent multivalue
- parameter's (gh-6832).
+* Added a new method `uri.values()` for representing multivalue parameters (gh-6832).
```
+> params = {q1 = uri.values("v1", "v2")}}
> uri.parse({"/tmp/unix.sock", params = params)
---
- host: unix/
diff --git a/changelogs/unreleased/gh-6833-decode-body-http-response.md b/changelogs/unreleased/gh-6833-decode-body-http-response.md
index cba6caae05..7f9fbbb4e6 100644
--- a/changelogs/unreleased/gh-6833-decode-body-http-response.md
+++ b/changelogs/unreleased/gh-6833-decode-body-http-response.md
@@ -1,7 +1,7 @@
## feature/lua/http client
-* New method "response:decode()" has been introduced. It allows to decode body
- to a Lua object when decoding function is available. Decode function depends
- on content type and following content types are supported by default:
- "application/json", "application/yaml" and "application/msgpack". Now user can
- define his own decode function (gh-6833).
+* 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).
diff --git a/changelogs/unreleased/gh-6833-encode-body-http-request.md b/changelogs/unreleased/gh-6833-encode-body-http-request.md
index 3d28cbac19..9caf0d785d 100644
--- a/changelogs/unreleased/gh-6833-encode-body-http-request.md
+++ b/changelogs/unreleased/gh-6833-encode-body-http-request.md
@@ -1,6 +1,7 @@
## feature/lua/http client
-* HTTP client is able to encode Lua objects automatically when it is possible.
- Encoding depends on content type passed to HTTP request and following types
- are supported: "application/json", "application/yaml" and
- "application/msgpack". Now user can define his own encoding function (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).
--
GitLab