chore: rename ctx to cx

docs/posts/11-arena-memo.md

@@ -2,13 +2,13 @@
 
 Dioxus differs slightly from other UI virtual doms in some subtle ways due to its memory allocator.
 
-One important aspect to understand is how props are passed down from parent components to children. All "components" (custom user-made UI elements) are tightly allocated together in an arena. However, because props and hooks are generically typed, they are casted to any and allocated on the heap - not in the arena with the components. 
+One important aspect to understand is how props are passed down from parent components to children. All "components" (custom user-made UI elements) are tightly allocated together in an arena. However, because props and hooks are generically typed, they are casted to any and allocated on the heap - not in the arena with the components.
 
-With this system, we try to be more efficient when leaving the component arena and entering the heap. By default, props are memoized between renders using COW and context. This makes props comparisons fast - done via ptr comparisons on the cow pointer. Because memoization is done by default, parent re-renders will *not* cascade to children if the child's props did not change.
+With this system, we try to be more efficient when leaving the component arena and entering the heap. By default, props are memoized between renders using COW and context. This makes props comparisons fast - done via ptr comparisons on the cow pointer. Because memoization is done by default, parent re-renders will _not_ cascade to children if the child's props did not change.
 
 https://dmitripavlutin.com/use-react-memo-wisely/
 
-This behavior is defined as an implicit attribute to user components. When in React land you might wrap a component is `react.memo`, Dioxus components are automatically memoized via an implicit attribute. You can manually configure this behavior on any component with "nomemo" to disable memoization. 
+This behavior is defined as an implicit attribute to user components. When in React land you might wrap a component is `react.memo`, Dioxus components are automatically memoized via an implicit attribute. You can manually configure this behavior on any component with "nomemo" to disable memoization.
 
 ```rust
 fn test() -> VNode {
@@ -21,9 +21,9 @@ fn test() -> VNode {
     }
 }
 
-static TestComponent: FC<()> = |ctx| html!{<div>"Hello world"</div>};
+static TestComponent: FC<()> = |cx| html!{<div>"Hello world"</div>};
 
-static TestComponent: FC<()> = |ctx| {
+static TestComponent: FC<()> = |cx| {
     let g = "BLAH";
     html! {
         <div> "Hello world" </div>
@@ -31,7 +31,7 @@ static TestComponent: FC<()> = |ctx| {
 };
 
 #[functional_component]
-static TestComponent: FC<{ name: String }> = |ctx| html! { <div> "Hello {name}" </div> };
+static TestComponent: FC<{ name: String }> = |cx| html! { <div> "Hello {name}" </div> };
 ```
 
 ## Why this behavior?
@@ -41,8 +41,8 @@ static TestComponent: FC<{ name: String }> = |ctx| html! { <div> "Hello {name}"
 Take a component likes this:
 
 ```rust
-fn test(ctx: Context<()>) -> VNode {
-    let Bundle { alpha, beta, gamma } = use_context::<SomeContext>(ctx);
+fn test(cx: Context<()>) -> VNode {
+    let Bundle { alpha, beta, gamma } = use_context::<SomeContext>(cx);
     html! {
         <div>
             <Component name=alpha />
@@ -53,4 +53,4 @@ fn test(ctx: Context<()>) -> VNode {
 }
 ```
 
-While the contents of the destructued bundle might change, not every child component will need to be re-rendered. 
+While the contents of the destructued bundle might change, not every child component will need to be re-rendered.