Refactor code structure for improved readability and maintainability

Author: xaviaracil

ob_v3p0/microsites/v3p0.md

@@ -247,7 +247,7 @@ In addition to the documentation in this section, there are [OpenAPI](#docs-open
 
 ### Architecture
 
-![Diagram showing the major components of the Open Badges API](./images/OB3_Architecture.svg)
+![Diagram showing the major components of the Open Badges API](v3p0/images/OB3_Architecture.svg)
 
 There are five key components to the API architecture.
 
@@ -547,7 +547,7 @@ There are two steps to dynamic client registration:
 1. Request a Service Description Document (SDD) from the [=resource server=]
 2. Register with the [=authorization server=]
 
-![Sequence diagram for registration](/standards/images/OB3_ACG_DynamicClientRegistration.svg)
+![Sequence diagram for registration](v3p0/images/OB3_ACG_DynamicClientRegistration.svg)
 
 The [=client=] only needs to register a `client_id` with the [=authorization server=] once. Each [=user=] will use the same `client_id` when they request their own authorization code.
 
@@ -735,7 +735,7 @@ When a registration error condition occurs, the authorization server returns an
 
 #### Obtaining Tokens
 
-![Sequence diagram for obtaining access tokens when using the ACG flow](/standards/images/OB3_ACG_ObtainingTokens.svg)
+![Sequence diagram for obtaining access tokens when using the ACG flow](v3p0/images/OB3_ACG_ObtainingTokens.svg)
 
 Obtaining an access token using an authorization code has two steps: