Modified the docs/docs-using-js-api-support.md file and the docs/docs-using-extending.md file

docs/docs-using-extending.md

@@ -11,7 +11,7 @@ will compile to a library (that is, `cargo init --lib`). Javy plugins are
 written as Wasm components but converted to Wasm modules during the
 initialization process.
 
-Your `Cargo.toml` should look like:
+Your `Cargo.toml` should look like the following data :
 
 ```toml
 [package]
@@ -27,7 +27,7 @@ javy-plugin-api = "4.0.0"
 wit-bindgen = "0.44.0"
 ```
 
-You'll need a WIT file in `wit/world.wit` that looks like:
+You'll need a WIT file in `wit/world.wit` that looks like the following code :
 
 ```wit
 package yournamespace:[email protected];
@@ -39,7 +39,7 @@ world my-javy-plugin {
 }
 ```
 
-If you want to use hostcalls in your plugin, you'll also need to include imports in your world. For example, if you wanted to import a function named `imported-function` that takes no arguments and doesn't return anything, it'll look like:
+If you want to use hostcalls in your plugin, you'll also need to include imports in your world. For example, if you wanted to import a function named `imported-function` that takes no arguments and doesn't return anything, it'll look like :
 
 ```wit
 package yournamespace:[email protected];
@@ -62,7 +62,7 @@ modules. See our documentation on
 [using complex data types in Wasm functions](./contributing-complex-data-types.md)
 for more details.
 
-For the world with the imported function, the `src/lib.rs` should look like:
+For the world with the imported function, the `src/lib.rs` should look like :
 
 ```rust
 use javy_plugin_api::{
@@ -102,7 +102,7 @@ javy_plugin!("my-javy-plugin", Component, config, modify_runtime);
 export!(Component);
 ```
 
-If you do not want to use the `javy_plugin!` macro for whatever reason, you can use the underlying APIs in `src/lib.rs` directly:
+If you do not want to use the `javy_plugin!` macro for whatever reason, you can use the underlying APIs in `src/lib.rs` directly :
 
 ```rust
 use std::process;

docs/docs-using-js-api-support.md

@@ -19,7 +19,6 @@ explicitly marked as partially supported in the table below.
 |`String.prototype.normalize`|✅| |
 |`TexDecoder`|🚧| Partial support, not fully compliant|
 |`TextEncoder`|🚧| Partial support, not fully compliant|
-|`TextEncoder`|🚧| Partial support, not fully compliant|
 |`console`|🚧| Partial support, `console.log` and `console.error`|
 
 Javy provides a custom `Javy` namespace, which includes the following