Futuresolo's changes to website/docs

Author: jsjolund

website/docs/advanced-topics/server-side-rendering.md

@@ -15,7 +15,7 @@ This approach works fine for most websites, with some caveats:
 
 1. Users will not be able to see anything until the entire WebAssembly
    bundle is downloaded and the initial render has been completed.
-   This can result in a poor user experience on a slow network.
+   This can result in a poor experience for users on a slow network.
 2. Some search engines do not support dynamically rendered web content and
    those who do usually rank dynamic websites lower in the search results.
 
@@ -26,7 +26,7 @@ To solve these problems, we can render our website on the server side.
 Yew provides a `ServerRenderer` to render pages on the
 server side.
 
-To render Yew components on the server-side, you can create a renderer
+To render Yew components on the server side, you can create a renderer
 with `ServerRenderer::<App>::new()` and call `renderer.render().await`
 to render `<App />` into a `String`.
 

website/docs/advanced-topics/struct-components/introduction.mdx

@@ -5,7 +5,7 @@ description: 'Components in Yew'
 
 ## What are Components?
 
-Components are the building blocks of Yew. They manage their state and can render themselves to the DOM.
+Components are the building blocks of Yew. They manage an internal state and can render elements to the DOM.
 Components are created by implementing the `Component` trait for a type.
 
 ## Writing Component's markup

website/docs/advanced-topics/struct-components/lifecycle.mdx

@@ -213,7 +213,7 @@ before it is destroyed. This method is optional and does nothing by default.
 ### Infinite loops
 
 Infinite loops are possible with Yew's lifecycle methods but are only caused when trying to update
-the same component after every rendering, when that update also requests the component to be rendered.
+the same component after every render, when that update also requests the component to be rendered.
 
 A simple example can be seen below:
 

website/docs/concepts/basic-web-technologies/css.mdx

@@ -7,7 +7,7 @@ comment: 'Keep this file as short and simple as possible. Its purpose is to ease
 import Tabs from '@theme/Tabs'
 import TabItem from '@theme/TabItem'
 
-Yew does not natively provide a CSS in Rust solution but helps with styling by providing
+Yew does not natively provide a CSS-in-Rust solution but helps with styling by providing
 programmatic ways to interact with the HTML `class` attribute.
 
 ## Classes

website/docs/concepts/basic-web-technologies/js.mdx

@@ -16,7 +16,7 @@ sometimes rely on calling JavaScript. What follows is an overview of the involve
 
 ## wasm-bindgen
 
-[`wasm-bindgen`](https://github.com/rustwasm/wasm-bindgen) is a library and tool that enables calls to JavaScript from Rust and back to Rust from JavaScript.
+[`wasm-bindgen`](https://github.com/rustwasm/wasm-bindgen) is a library and tool that bridges calls between JavaScript and Rust functions.
 
 We highly recommend you take a look at their [documentation](https://rustwasm.github.io/docs/wasm-bindgen/) and our [quick guide](./wasm-bindgen.mdx).
 

website/docs/concepts/basic-web-technologies/wasm-bindgen.mdx

@@ -38,7 +38,7 @@ for translating between the two. Using this macro is more advanced, and you shou
 for it unless you are trying to use an external JavaScript library. The `js-sys` and `web-sys`
 crates expose `wasm-bindgen` definitions for built-in JavaScript types and browser APIs.
 
-Let's go over a simple example of using the `#[wasm-bindgen]` macro to import some specific flavors
+Let's go over a simple example of using the `#[wasm-bindgen]` macro to import some specific flavours
 of the [`console.log`](https://developer.mozilla.org/en-US/docs/Web/API/Console/log) function.
 
 ```rust ,no_run
@@ -204,8 +204,9 @@ There are three main interfaces in this crate currently:
 
 1. [`JsFuture`](https://rustwasm.github.io/wasm-bindgen/api/wasm_bindgen_futures/struct.JsFuture.html) -
    A type that is constructed with a [`Promise`](https://rustwasm.github.io/wasm-bindgen/api/js_sys/struct.Promise.html)
-   and can then be used as a `Future<Output=Result<JsValue, JsValue>>`. This Rust future will resolve
-   or reject the value coming out of the `Promise`.
+   and can then be used as a `Future<Output=Result<JsValue, JsValue>>`. This `Future` will resolve to `Ok` if
+   the `Promise` is resolved and `Err` if the `Promise` is rejected, containing the resolved or rejected
+   value from the `Promise` respectively.
 
 2. [`future_to_promise`](https://rustwasm.github.io/wasm-bindgen/api/wasm_bindgen_futures/fn.future_to_promise.html) -
    Converts a Rust `Future<Output=Result<JsValue, JsValue>>` into a

website/docs/concepts/basic-web-technologies/web-sys.mdx

@@ -13,7 +13,7 @@ procedurally generated from browser WebIDL which is why some names are so long a
 
 The `web-sys` crate with all of its features enabled can add lots of bloat to a Wasm application.
 To get around this issue most types are feature gated so that you only include the types
-you require for your application. Yew includes several features from `web-sys` and
+you require for your application. Yew enables several features from `web-sys` and
 exposes some types in its public API. You will often need to add `web-sys` as a dependency yourself.
 
 ## Inheritance in `web-sys`
@@ -128,8 +128,8 @@ fn with_jscast(node_ref: NodeRef) {
 
 ## JavaScript example to Rust
 
-This section shows that examples which use JavaScript to interact with the Web APIs
-can be adapted and written using Rust with `web-sys`.
+This section demonstrates examples of how JavaScript code which interact with the
+Web APIs can be rewritten with `web-sys` in Rust.
 
 ### JavaScript example
 

website/docs/concepts/function-components/hooks/custom-hooks.mdx

@@ -4,7 +4,7 @@ title: 'Custom Hooks'
 
 ## Defining custom Hooks
 
-A component's stateful logic can be extracted into reusable functions by creating custom Hooks.
+The stateful logic of a component can be extracted into reusable functions by creating custom Hooks.
 
 Consider that we wish to create an event listener that listens to an event on the `window`
 object.
@@ -34,13 +34,13 @@ pub fn show_storage_changed() -> Html {
 ```
 
 There's one problem with this code: the logic can't be reused by another component.
-If we build another component that keeps track of the event,
+If we build another component that listens to a different event,
 instead of copying the code, we can move the logic into a custom hook.
 
 We'll start by creating a new function called `use_event`.
 The `use_` prefix denotes that a function is a hook.
 This function will take an event target, an event type, and a callback.
-All hooks must be marked by `#[hook]` to function.
+All hooks must be marked by `#[hook]` on their function definition.
 
 ```rust
 use web_sys::{Event, EventTarget};

website/docs/concepts/function-components/hooks/introduction.mdx

@@ -7,7 +7,7 @@ slug: /concepts/function-components/hooks
 
 Hooks are functions that let you store state and perform side effects.
 
-Yew comes with a few pre-defined Hooks. You can also create your own or discover many [community-made hooks](/community/awesome#hooks).
+Yew comes with a few pre-defined hooks. You can also create your own or discover many [community-made hooks](/community/awesome#hooks).
 
 ## Rules of hooks
 

website/docs/concepts/function-components/properties.mdx

@@ -18,7 +18,7 @@ A type has to implement the `Properties` trait before it can be used as the prop
 
 ## Reactivity
 
-Yew checks if Props have changed when reconciling the virtual DOM during re-rendering, to know if nested components need to be re-rendered.
+Yew checks if props have changed when reconciling the Virtual DOM during re-rendering, to know if nested components need to be re-rendered.
 This way Yew can be considered a very reactive framework, as changes from the parent will always be propagated downward,
 and the view will never be out of sync with the data coming from props/state.
 
@@ -102,7 +102,7 @@ fn App() -> Html {
 ## Derive macro field attributes
 
 When deriving `Properties` all fields are required by default.
-The following attributes allow you to give your props default values which will be used when a parent has not set them.
+The following attributes allow you to give your props default values which will be used when the parent has not set them.
 
 :::tip
 Attributes aren't visible in Rustdoc generated documentation.