diff --git a/packages/yew/src/dom_bundle/bnode.rs b/packages/yew/src/dom_bundle/bnode.rs
index fd876a39bb4..79586b70361 100644
--- a/packages/yew/src/dom_bundle/bnode.rs
+++ b/packages/yew/src/dom_bundle/bnode.rs
@@ -266,11 +266,11 @@ mod feat_hydration {
                 }
                 // You cannot hydrate a VRef.
                 VNode::VRef(_) => {
-                    panic!("VRef is not hydratable. Try move it to a component mounted after an effect.")
+                    panic!("VRef is not hydratable. Try moving it to a component mounted after an effect.")
                 }
                 // You cannot hydrate a VPortal.
                 VNode::VPortal(_) => {
-                    panic!("VPortal is not hydratable. Try to create your portal by delaying it with use_effect.")
+                    panic!("VPortal is not hydratable. Try creating your portal by delaying it with use_effect.")
                 }
                 VNode::VSuspense(vsuspense) => {
                     let (node_ref, suspense) =
diff --git a/website/docs/advanced-topics/server-side-rendering.md b/website/docs/advanced-topics/server-side-rendering.md
index 51549987a44..7c0d90ed9c0 100644
--- a/website/docs/advanced-topics/server-side-rendering.md
+++ b/website/docs/advanced-topics/server-side-rendering.md
@@ -159,7 +159,7 @@ them into an `use_effect` hook.
 
 Whilst it's possible to use Struct Components with server-side rendering in
 hydration, the components will be created in a different order than they
-are directly rendered on the client-side. The render function will be called
+are directly rendered on the client-side. The view function will be called
 multiple times before the rendered function will be called and the
 component will start receiving messages immediately after the `view()`
 function is called after the first time. At that time, the DOM may not