fixup! Expose the ECIES support from vodozemac

Author: poljar

src/vodozemac/ecies.rs

@@ -41,7 +41,9 @@ pub struct Ecies {
 impl Ecies {
     /// Create a new, random, unestablished ECIES session.
     ///
-    /// This method will use the `MATRIX_QR_CODE_LOGIN` info.
+    /// This method will use the
+    /// [`MATRIX_QR_CODE_LOGIN`](https://github.com/matrix-org/matrix-spec-proposals/pull/4108)
+    /// info for domain separation when creating the session.
     #[wasm_bindgen(constructor)]
     pub fn new() -> Self {
         let inner = ecies::Ecies::new();
@@ -140,16 +142,16 @@ impl EstablishedEcies {
     /// Get the [`CheckCode`] which uniquely identifies this
     /// [`EstablishedEcies`] session.
     ///
-    /// This check code can be used to check that both sides of the session are
-    /// indeed using the same shared secret.
+    /// This check code can be used to verify and confirm that both sides of the
+    /// session are indeed using the same shared secret.
     pub fn check_code(&self) -> CheckCode {
         self.inner.lock().unwrap().check_code().into()
     }
 }
 
 /// A check code that can be used to confirm that two [`EstablishedEcies`]
 /// objects share the same secret. This is supposed to be shared out-of-band to
-/// protect against active MITM attacks.
+/// protect against active Man-in-the-middle (MITM) attacks.
 ///
 /// Since the initiator device can always tell whether a MITM attack is in
 /// progress after channel establishment, this code technically carries only a