Requirements,-Design-and-Approach.md

 **1. Introduction**<br/>
- &nbsp;&nbsp;&nbsp; 1.1 Purpose of this document<br/>
+ &nbsp;&nbsp;&nbsp;** 1.1 Purpose of this document**<br/>
   &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;        The objective of this document is to provide functional and non-functional requirements for OSDU Admin UI development team to develop a front-end project for accessing existing API which are currently invoked by Postman. This solution will ease up a lot of admin tasks with the intended UI.<br/>
- &nbsp;&nbsp;&nbsp;  1.2 Project Background<br/>
+ &nbsp;&nbsp;&nbsp;  **1.2 Project Background**<br/>
          Various parts of OSDU have functions with a need for an OSDU admin person to make changes to the settings. However, at this moment these changes have to be made in different parts of OSDU and that really is not ok for an R3 Production release. For this reason, this request for an OSDU Forum Member Company to drive the development of an Admin functions within OSDU R3.<br/>
- &nbsp;&nbsp;&nbsp;  1.3 Project Objectives and Scope<br/>
-     &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;  1.3.1 Objective<br/>
+ &nbsp;&nbsp;&nbsp; ** 1.3 Project Objectives and Scope**<br/>
+     &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;  **1.3.1 Objective**<br/>
       &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;       The objective of this project is to make the day to day work of an admin simpler by providing a UI for admin tasks. Currently these tasks are performed via Postman by invoking individual APIs.<br/>
-   &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;   1.3.2 In-scope<br/>
\ No newline at end of file
+   &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;   **1.3.2 In-scope**<br/>
\ No newline at end of file