Edits to text in refresh docs (#39188)

docs/reference/docs/refresh.asciidoc

@@ -46,7 +46,7 @@ compared to `true`. In the case that the index is only changed once every
 `index.refresh_interval` then it saves no work.
 * `true` creates less efficient indexes constructs (tiny segments) that must
 later be merged into more efficient index constructs (larger segments). Meaning
-that the cost of `true` is payed at index time to create the tiny segment, at
+that the cost of `true` is paid at index time to create the tiny segment, at
 search time to search the tiny segment, and at merge time to make the larger
 segments.
 * Never start multiple `refresh=wait_for` requests in a row. Instead batch them
@@ -58,7 +58,7 @@ causes a refresh. Conversely, setting `index.refresh_interval` to something
 shorter than the default like `200ms` will make `refresh=wait_for` come back
 faster, but it'll still generate inefficient segments.
 * `refresh=wait_for` only affects the request that it is on, but, by forcing a
-refresh immediately, `refresh=true` will affect other ongoing request. In
+refresh immediately, `refresh=true` will affect other ongoing requests. In
 general, if you have a running system you don't wish to disturb then
 `refresh=wait_for` is a smaller modification.