doc updates

emer · Mar 9, 2024 · 716d725 · 716d725
1 parent ef2e3f7
commit 716d725
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/egui/README.md b/egui/README.md
@@ -6,11 +6,11 @@ The [ra25](https://github.com/emer/axon/tree/master/examples/ra25) example has a
 
 # Examples
 
-Here's the start of the main ConfigGui method:
+Here's the start of the main ConfigGUI method:
 
 ```Go
-// ConfigGui configures the GoGi gui interface for this simulation,
-func (ss *Sim) ConfigGui() *gi.Window {
+// ConfigGUI configures the Cogent Core GUI interface for this simulation.
+func (ss *Sim) ConfigGUI() *gi.Window {
 	title := "Leabra Random Associator"
 	ss.GUI.MakeWindow(ss, "ra25", title, `This demonstrates a basic Leabra model. See <a href="https://github.com/emer/emergent">emergent on GitHub</a>.</p>`)
 	ss.GUI.CycleUpdateInterval = 10

diff --git a/elog/README.md b/elog/README.md
@@ -401,7 +401,7 @@ First, initialize the ActRFs in the `ConfigLogs` function, using strings that sp
     ss.Stats.InitActRFs(ss.Net, []string{"V4:Image", "V4:Output", "IT:Image", "IT:Output"}, "ActM")
 ```
 
-To add tabs in the gui to visualize the resulting RFs, add this in your `ConfigGui` (note also adding a tab to visualize the input Image that is being presented to the network):
+To add tabs in the gui to visualize the resulting RFs, add this in your `ConfigGUI` (note also adding a tab to visualize the input Image that is being presented to the network):
 
 ```Go
     tg := ss.GUI.TabView.AddNewTab(etview.KiT_TensorGrid, "Image").(*etview.TensorGrid)

diff --git a/stepper/README.md b/stepper/README.md
@@ -115,7 +115,7 @@ and (optionally) `stepper.StopCheckFn` functions:
 8. Add code to the user interface to start, pause, and stop the simulation:
 
    ```go
-   func (ss *Sim) ConfigGui() *gi.Window {
+   func (ss *Sim) ConfigGUI() *gi.Window {
       ...
       tbar.AddAction(gi.ActOpts{Label: "Stop", Icon: "stop",
          Tooltip: "Stop the current program at its next natural stopping point (i.e., cleanly stopping when appropriate chunks of computation have completed).",