docs: fix md to meet format check (#72)

governance/meetings/README.md

@@ -2,9 +2,9 @@
 
 ## 2023
 
-* [2023-06-14](uportal-steering-committee-2023-06-14.md)
-* [2023-05-10](uportal-steering-committee-2023-05-10.md)
-* [2023-03-08](uportal-steering-committee-2023-03-08.md)
+*   [2023-06-14](uportal-steering-committee-2023-06-14.md)
+*   [2023-05-10](uportal-steering-committee-2023-05-10.md)
+*   [2023-03-08](uportal-steering-committee-2023-03-08.md)
 
 ## 2022
 

governance/meetings/uportal-steering-committee-2023-05-10.md

@@ -20,7 +20,7 @@ In the "FOSS For Education" community track there will be some uPortal presentat
 There are few 30-minute calls in the works focused on developers, contributors, and the user community.
 Topics include:
 
-* Roadmap technicalities
-* Website plans
+*   Roadmap technicalities
+*   Website plans
 
 Watch the mailing lists and this space for the call info.

governance/meetings/uportal-steering-committee-2023-06-14.md

@@ -11,14 +11,14 @@ Jim Helwig, Chris Beach, Julien Gribonvald, Jim Helwig, Laura Moran, Benito Gonz
 The **[Free and Open Source Yearly (FOSSY) conference](https://2023.fossy.us)** will be taking place 13 to 16 of July in Portland, OR.
 In the "[FOSS For Education](https://2023.fossy.us/pages/tracks/#education)" community track there will be some uPortal presentations at this inaugural conference. At the time of writing, the following proposal(s) have been accepted:
 
-- Open Standards in Higher Ed and the Challenges of Interoperability
+-   Open Standards in Higher Ed and the Challenges of Interoperability
 
 ### uPortal Call for Developers and (Implementing) Institutions
 
 There are few 30-minute calls in the works focused on developers, contributors, and the user community.
 
-* [uPortal technical call](https://groups.google.com/u/2/a/apereo.org/g/uportal-dev/c/VeblfMLWabI): Friday June 23 at 11:00 AM (Pacific)
-* An implementor-focused call is planned for the end of July
+*   [uPortal technical call](https://groups.google.com/u/2/a/apereo.org/g/uportal-dev/c/VeblfMLWabI): Friday June 23 at 11:00 AM (Pacific)
+*   An implementor-focused call is planned for the end of July
 
 Watch the mailing lists and this space for the call info.
 

manuals/en/uportal5-manual/configure/ga4/ga4.md

@@ -15,19 +15,19 @@ needed files in your environment, if you are not able to upgrade.
 Google Analytics 4, like Google Universal Analytics, is implemented in two files within the
 uPortal Google Analytics Portlet.
 
-- init.jsp
-- up-ga.js
+-   init.jsp
+-   up-ga.js
 
 Within the community version of uPortal, these files are located within the uPortal-webapp project
 
-- src/main/webapp/WEB-INF/jsp/GoogleAnalytics/init.jsp
-- src/main/webapp/media/skins/common/javascript/uportal/up-ga.js
+-   src/main/webapp/WEB-INF/jsp/GoogleAnalytics/init.jsp
+-   src/main/webapp/media/skins/common/javascript/uportal/up-ga.js
 
 To use these files without using the uPortal community version but within uportal-start, put these
 two files in the overlays folder
 
-- overlays/uPortal/src/main/webapp/WEB-INF/jsp/GoogleAnalytics/init.jsp
-- overlays/uPortal/src/main/webapp/media/skins/common/javascript/uportal/up-ga.js
+-   overlays/uPortal/src/main/webapp/WEB-INF/jsp/GoogleAnalytics/init.jsp
+-   overlays/uPortal/src/main/webapp/media/skins/common/javascript/uportal/up-ga.js
 
 ### init.jsp
 
@@ -62,13 +62,13 @@ the event to be immutable.
 
 The overall structure of the updated up-ga.js script is similar to the original script with several exceptions:
 
-- Several functions return values that will be included in the up.gtag("event") body, rather than put directly
+-   Several functions return values that will be included in the up.gtag("event") body, rather than put directly
 into the configuration of the ga("event")
-- Due to dependencies, some functions have been reordered.
-- The up.gtag javascript object contains the needed code for executing the needed events, whereas the original script
+-   Due to dependencies, some functions have been reordered.
+-   The up.gtag javascript object contains the needed code for executing the needed events, whereas the original script
 did not need to be added to the up structure.  At the time, this was required to have visibility into the Google
 Analytics 4 functions.  This could be revisited if the current implementation has issues.
-- Google Universal Analytics sends individual events.  GA4 collects events and sends them in batch, approximately event
+-   Google Universal Analytics sends individual events.  GA4 collects events and sends them in batch, approximately event
 10 seconds.
 
 ## Configuration Changes
@@ -77,6 +77,6 @@ The biggest change is the need to create and use the Google Analytics 4 tag.  Go
 a "UA-" prefix.  GA4 tags begin with a "G-" prefix.  You create the new GA4 tag from within the Google Analytics website within the Admin
 function.  Once you have created this new tag, you will need to deploy it to the portlet via a dataImport.
 
-1. Modify the file portlet-definition/google-analytics-config/portlet-definition.xml where you store your portlet definitions.
-2. Within that file, replace the UA- value of the "propertyId" field with the new G- prefixed value and save.
-3. Perform a dataImport to load the new portlet definition.
+1.  Modify the file portlet-definition/google-analytics-config/portlet-definition.xml where you store your portlet definitions.
+2.  Within that file, replace the UA- value of the "propertyId" field with the new G- prefixed value and save.
+3.  Perform a dataImport to load the new portlet definition.