chore: update changelogs

README.md

@@ -57,7 +57,7 @@ the developer to remember a terminal command or change anything outside the proj
 - Create a [build script][build-script-explanation] and provide cargo with the path to the libraries with `cargo:rustc-link-search=` and `cargo:rustc-link-lib=static=`.
 
 ##### Troubleshooting
-In real-world scenarios, one will use Rust to cross compile a library (e.g. Android and iOS). Therefore, we need both `cdylib` as well as the `staticlib` as crate-type. If you compile as usual with cargo build (e.g.: `cargo build --target aarch64-apple-ios --release`) it will not work, because cargo tries to build the dylib as well. Fortunately, since rust 1.64. there is a new option for [rustc](https://github.com/rust-lang/cargo/issues/10083) in the stable channel. Because of this, the following will work: `cargo rustc --crate-type staticlib --lib --target aarch64-apple-ios --release` 
+In real-world scenarios, one will use Rust to cross compile a library (e.g. Android and iOS). Therefore, we need both `cdylib` as well as the `staticlib` as crate-type. If you compile as usual with cargo build (e.g.: `cargo build --target aarch64-apple-ios --release`) it will not work, because cargo tries to build the dylib as well. Fortunately, since rust 1.64. there is a new option for [rustc](https://github.com/rust-lang/cargo/issues/10083) in the stable channel. Because of this, the following will work: `cargo rustc --crate-type staticlib --lib --target aarch64-apple-ios --release`
 
 ### Execution
 Executables compiled with a dynamic lib must have access to the vosk library at runtime. Executables compiled with a statically compiled library do not.

crates/vosk-sys/CHANGELOG.md

@@ -1,5 +1,8 @@
+# 0.2.0
+* Add support for Batch recognition ([PR](https://github.com/Bear-03/vosk-rs/pull/8)).
+
 # 0.1.1
-* Documentation fixes
+* Documentation fixes.
 
 # 0.1.0
-* First release (bindings for Vosk v0.3.42)
+* First release.

crates/vosk/CHANGELOG.md

@@ -1,8 +1,17 @@
+# 0.3.0
+* Add support for Batch recognition ([PR](https://github.com/Bear-03/vosk-rs/pull/8)).
+* [BREAKING] Redesign `LogLevel` to adequately represent Kaldi log levels ([PR](https://github.com/Bear-03/vosk-rs/pull/9)).
+* [BREAKING] `Recognizer::accept_waveform` methods now return `Result<T, AcceptWaveformError>` (previously `T`).
+  Vosk takes the buffer length as an `i32` so the user should be able to handle errors that arise due to the
+  buffer being longer than `i32::MAX`.
+* [BREAKING] `Model::find_word` now returns `Option<u32>` (previously `Option<u16>`) to adjust it to the values
+  that Vosk can return.
+
 # 0.2.0
-* Documentation fixes
-* Loosen bounds for Recognizer::new_with_grammar
-* [BREAKING] Extra double quotes are no longer needed for phrases in `Recognizer::new_with_grammar`
+* Documentation fixes.
+* Loosen bounds for Recognizer::new_with_grammar.
+* [BREAKING] Extra double quotes are no longer needed for phrases in `Recognizer::new_with_grammar`.
 
 # 0.1.0
-* First release
+* First release.
 

crates/vosk/src/models/sequential.rs

@@ -37,7 +37,7 @@ impl Model {
         if symbol == -1 {
             None
         } else {
-            // UNWRAP: the only negative symbol possible was -1
+            // UNWRAP: the only possible negative symbol was -1
             Some(u32::try_from(symbol).unwrap())
         }
     }