fix(specs): use periods in description fields consistently

[kai687]

🧭 What and Why

Many sentences in description fields didn't end in periods, although more sentences followed. I believe this was introduced in PR #5125 by accident.

🎟 JIRA Ticket: N/A

Changes included:

• Make sure every sentence ends in a period
• Use periods in list items consistently
• Fix typo in specs/common/schemas/Batch.yml

🧪 Test

N/A

[algolia-api-clients-automation-bot]

✔️ Code generated!

Name	Link
🪓 Triggered by	6482db9c0b3d557d99f46add192fa817cd101d6b
🍃 Generated commit	6c152b893dbc20d0abcac16783576c5610831910
🌲 Generated branch	generated/fix/description-periods

📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language	Req/s
javascript	2312
php	2262
go	1823
python	1458
csharp	1417
ruby	1290
java	1100
swift	982
scala	659

[eric-zaharia]

This is great, thank you!

[xroche]

Posted on the wrong PR by mistake, sorry for the noise. The review belongs on #6790 and is now there.

On this PR: the punctuation pass looks right, and the one non-punctuation edit is correct. partialUpdateObject with createIfNoExists: true does add the record, so "this action adds the record to the index" is accurate. No period landed mid-sentence, which was the real risk in a | block scalar where Markdown joins consecutive lines.

Optional, all pre-existing and inside blocks this PR already edits:

• Four sentences still have no period: attributesToHighlight and attributesToRetrieve ("Attribute names are case-sensitive"), minProximity ("by equally scoring matches that are farther apart"), and two lines in responseFields.
• Two grammar errors survive on lines this PR rewrote: "considered an exact matches" in alternativesAsExact, and "a more broader search" in similarQuery.
• Batch.yml leaves - \delete`. Delete an index.with a period where its siblings use- `key`: description`.