@@ -11,7 +11,7 @@ Implementation tracked by: https://github.com/openedx/edx-platform/issues/36215
1111Context
1212*******
1313
14- OEP-45 declares that sites will configure each IDA's (indepently -deployable
14+ OEP-45 declares that sites will configure each IDA's (independently -deployable
1515application's) Django settings with an ``<APPNAME>_CFG `` YAML file, parsed and
1616loaded by a single upstream-provided ``DJANGO_SETTINGS_MODULE ``. This contrasts
1717with the Django convention, which is that sites override Django settings using
@@ -133,7 +133,7 @@ cited as a chief area of pain for Open edX developers and operators.
133133Discussions in the Named Release Planning and Build-Test-Release Working Groups
134134frequently are encumbered with confusion and uncertainty of what the default
135135settings are in edx-platform, how they differ from Tutor's default settings,
136- what settings can be overriden , and how to do so. Only a minority of developers
136+ what settings can be overridden , and how to do so. Only a minority of developers
137137and operators fully understand the configuration logic described above
138138end-to-end; even for those that do, following this override chain for any given
139139Django setting is time-consuming and error-prone. CAT-1 bugs and high-severity
@@ -170,7 +170,7 @@ that we are landing on a solid settings structure for edx-platform, we'll
170170propose an OEP-45 update to generalize the structure to all deployable Open edX
171171Django applications.
172172
173- Finally, based on what we learn throughout this process, our OEP-45 propsal
173+ Finally, based on what we learn throughout this process, our OEP-45 proposal
174174will either recommend to:
175175
1761761. Drop support for the ``<APPNAME>_CFG `` YAML files, or
@@ -181,7 +181,7 @@ will either recommend to:
181181
182182At the time, we do not have enough information whether option 1 or 2 would be
183183more beneficial overall to the community.
184- `The discussion on this sub-decisision will continue on this GitHub issue <https://github.com/openedx/open-edx-proposals/issues/684 >`_.
184+ `The discussion on this sub-decision will continue on this GitHub issue <https://github.com/openedx/open-edx-proposals/issues/684 >`_.
185185
186186Target settings structure for edx-platform
187187==========================================
@@ -304,7 +304,7 @@ These steps are non-breaking unless noted.
304304 providers that use these settings modules, as they will either need to
305305 maintain local copies of these modules, or "rebase" their internal
306306 settings modules onto (cms,lms)/envs/common.py. Update operator
307- documenation as needed.
307+ documentation as needed.
308308
309309 2. Update OEP-45 to clarify that YAML configuration is
310310 optional. Operators can opt out of YAML by deriving directly from
@@ -332,7 +332,7 @@ Here is an alternate structure that would de-dupe any shared LMS/CMS dev & test
332332logic by creating more shared modules within openedx/envs folder. Although
333333DRYer, this structure would increase the total number of edx-platform files and
334334potentially encourage more LMS-CMS coupling. So, we will not pursue this
335- structure, but will keep it in mind as an alternative if we enounter
335+ structure, but will keep it in mind as an alternative if we encounter
336336difficulties with the plan laid out in this ADR.
337337
338338* ``openedx/envs/common.py ``
0 commit comments