feat: add what-to-remember sections

Co-authored-by: Copilot <copilot@github.com>

Author: wakonig

docs/learn/devices/introduction-to-ophyd.md

@@ -124,6 +124,14 @@ The device-and-signal model makes it possible to:
 
 That makes ophyd a practical abstraction layer for scientific instrumentation software.
 
+!!! info "What to remember"
+    - In ophyd, a `Signal` models one value and a `Device` groups related signals.
+    - `Component` declarations define a reusable device structure that can be instantiated with
+      different prefixes.
+    - `read()` and `read_configuration()` serve different purposes.
+    - `Kind` controls whether a signal behaves like measured data, configuration data, or is
+      omitted from normal reads.
+
 ## What to read next
 
 If you are learning ophyd specifically for BEC, the next useful pages are:

docs/learn/file-writer/introduction.md

@@ -27,3 +27,10 @@ BEC file writing is organized around a few distinct pieces:
 - plugin-provided writer classes, which can extend that structure
 - file references, which let devices announce externally created files so they can be linked into the master file
 - async writing, which continuously writes data while the scan is still running
+
+!!! info "What to remember"
+    - BEC writes scan data to HDF5 files after every scan.
+    - The default layout is defined by `DefaultFormat` and does not strictly enforce NeXuS.
+    - Beamlines can extend or replace the default layout through a plugin-provided writer class.
+    - Devices can link externally created files into the master file using file references.
+    - Async writing keeps data flowing into the file while the scan is still in progress.

docs/learn/gui/introduction.md

@@ -81,6 +81,13 @@ data updates, Qt property support, and RPC exposure for user-facing methods. In
 is used to build beamline-specific views that can then be reused in BEC Designer, the Dock Area,
 and scripted RPC workflows.
 
+!!! info "What to remember"
+    - BEC Widgets runs in a separate process, so GUI load does not affect scan execution.
+    - Live widget updates come from Redis events through the BEC Dispatcher into Qt signals/slots.
+    - You can build UIs in four ways: BEC Designer, Dock Area profiles, RPC scripting, or custom
+      `BECWidget` subclasses.
+    - GUI workflows can stay fully graphical, fully scripted, or mixed in the same experiment.
+
 ## What to read next
 
 - [RPC GUI Control](rpc-gui-control.md) explains how the BEC IPython client communicates with