making some paragraphs instead of point form

Author: LadyBluenotes

src/routes/reference/basic-reactivity/create-signal.mdx

@@ -209,12 +209,9 @@ setName("Jane"); // Logs: "Hello, Jane!"
 
 ### Equality Checking
 
-By default, signals use strict equality (`===`) to determine if a value has changed:
-
-- Primitive values are compared by value
-- Objects and arrays are compared by reference
-- Setting a signal to the same reference won't trigger updates
-- Setting a signal to a new object with identical properties will trigger updates
+By default, signals use strict equality (`===`) to determine if a value has changed. 
+This means primitive values are compared by value, while objects and arrays are compared by reference. 
+Setting a signal to the same reference will not trigger updates, but setting it to a new object or array, even if it has identical properties, will trigger updates.
 
 ### Function Values
 
@@ -236,15 +233,12 @@ The outer function is the updater, the inner function is your actual value.
 
 ### Development vs Production
 
-**Development mode:**
-- Signals track additional metadata for debugging
-- The `name` option provides useful names in dev tools
-- Warnings are issued for signals created outside reactive contexts
+In development mode, signals track additional metadata to aid debugging. 
+The `name` option allows you to assign meaningful names to signals, making them easier to identify in developer tools. 
+Additionally, Solid issues warnings if signals are created outside of reactive contexts, helping you catch potential issues early.
 
-**Production mode:**
-- Debugging metadata is stripped
-- Dev-only options like `name` are ignored
-- No warnings are issued
+In production mode, all debugging metadata is stripped away for optimal performance. 
+Dev-only options like `name` are ignored, and no warnings are issued, ensuring that your application runs as efficiently as possible.
 
 ### Error Handling