From acd775aca0a52a6fd89c8c3d9d2c4d1f5b2919c8 Mon Sep 17 00:00:00 2001 From: Feanil Patel Date: Mon, 25 Sep 2023 11:09:17 -0400 Subject: [PATCH] docs: Apply suggestions from code review Co-authored-by: Ned Batchelder Co-authored-by: Deborah Kaplan --- .../oep-0067-bp-tools-and-technology.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/oeps/best-practices/oep-0067-bp-tools-and-technology.rst b/oeps/best-practices/oep-0067-bp-tools-and-technology.rst index 51a75eb37..41f63c255 100644 --- a/oeps/best-practices/oep-0067-bp-tools-and-technology.rst +++ b/oeps/best-practices/oep-0067-bp-tools-and-technology.rst @@ -33,24 +33,24 @@ OEP-67: Standard Tools and Technologies Abstract ******** -The Open edX Platform is built using many 1st and 3rd party tools and technologies. +The Open edX Platform is built using many first- and third-party tools and technologies. This document covers the current recommendations for which tools and technologies should be used. Motivation ********** -The Open edX platform has a lot of 1st and 3rd party tools and technology that it uses. +The Open edX platform has a lot of first and third party tools and technology that it uses. The problems we're trying to solve are: - * It is difficult to know what the current best practice for a given area. + * It is difficult to know the current best practice for a given area. - * It is unclear how to go about the discussion and decision making process + * It is unclear how to go about the discussion and decision-making process to change a best practice. :doc:`OEP-11 ` serves as a great example for the usefulness of this kind of OEP but limits itself to be relevant only to frontend technologies. This OEP would supersede :doc:`OEP-11 -` and encompass not only frontend technolog but any +` and encompass not only front-end technology but any technology that: * Is considered a best practice for the Open edX Platform