Adjust some wording

rustwasm · Jan 11, 2025 · e7cb0be · e7cb0be
1 parent f5f779c
commit e7cb0be
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/crates/cli-support/src/wit/nonstandard.rs b/crates/cli-support/src/wit/nonstandard.rs
@@ -74,7 +74,7 @@ pub struct AuxExport {
     /// Comments parsed in Rust and forwarded here to show up in JS bindings.
     pub comments: String,
     /// Function's argument info in Rust forwarded here to configure the signature
-    /// that show up in bindings.
+    /// that shows up in bindings.
     pub args: Option<Vec<AuxFunctionArgumentData>>,
     /// Whether this is an async function, to configure the TypeScript return value.
     pub asyncness: bool,

diff --git a/guide/src/reference/attributes/on-rust-exports/function-attributes.md b/guide/src/reference/attributes/on-rust-exports/function-attributes.md
@@ -5,7 +5,7 @@ By default, exported Rust functions and methods generate function signature from
 - `#[wasm_bindgen(js_name)]`, `#[wasm_bindgen(unchecked_param_type)]` and `#[wasm_bindgen(param_description)]` applied to a Rust function argument to override that argument's name and type and to specify descriptions for generated JS/TS bindings.
 
 > **NOTE**:
-> Types that are provided using `#[wasm_bindgen(unchecked_return_type)]` and `#[wasm_bindgen(unchecked_param_type)]` aren't checked as these attributes' identifiers entail, meaning they will end up in the function's signature and docs bindings exactly as they have been specified and there are no checks/validation for them in place, so only because a user uses `#[wasm_bindgen(unchecked_param_type = "number")]` for example, it doesn't necessarily mean it's actually going to be a value of number type, therefore validation and checks between the value and its type should be handled by the user and the responsibility of using them correctly and carefully relies solely on the user.
+> Types that are provided using `#[wasm_bindgen(unchecked_return_type)]` and `#[wasm_bindgen(unchecked_param_type)]` aren't checked for their contents. They will end up in function signature and JSDoc exactly as they have been specified. E.g. `#[wasm_bindgen(unchecked_return_type = "number")]` on a function returning `String` will return a `string`, not a `number`, even if the TS signature and JSDoc will say otherwise.
 
 Let's look at some exmaples:
 ```rust