fixed typo
Change-Id: I7051c40cf5001a2a76b7f7729f8090c3826446f4
diff --git a/onramp/blueprints.rst b/onramp/blueprints.rst
index f7ad4cb..775c74c 100644
--- a/onramp/blueprints.rst
+++ b/onramp/blueprints.rst
@@ -32,9 +32,15 @@
By standardizing the process for adding new blueprints to OnRamp, the
goal is to encourage the community to contribute (and maintain) new
-Aether configurations and deployment scenarios. The rest of this
+Aether configurations and deployment scenarios.\ [#]_ The rest of this
section documents community-contributed blueprints to-date.
+.. [#] Not all possible configurations of Aether require a
+ blueprint. There are other ways to add variability, for
+ example, by documenting simple ways to modify an existing
+ blueprint. Disabling ``core.standalone`` and selecting an
+ alternative ``core.values_file`` are two common examples.
+
Multiple UPFs
~~~~~~~~~~~~~~~~~~~~~~
@@ -86,7 +92,7 @@
$ make gnbsim-install
You can also optionally install the monitoring subsystem. Note that
-because ``main.yml`` sets ``core.standalone: "false"``), any models
+because ``main.yml`` sets ``core.standalone: "false"``, any models
loaded into ROC are automatically applied to SD-Core.
At this point you are ready to bring up additional UPFs and bind them