fix(README): fix inline notes formatting

Author: awpala

README.md

@@ -81,7 +81,7 @@ yarn build
 yarn dev
 ```
 
-> ![NOTE]
+> [!NOTE]
 > A cloud-based Firebase project must still exist in order to run the emulator locally in this manner. Simply create a blank/empty [Firebase](https://firebase.google.com/) project using a Google account for this purpose, and then populate file `website/.env` accordingly with corresponding API key and project information from Firebase (see `website/example.env` for additional reference, as well as `website/__seed__/README.md` for more information regarding seeding a cloud-based Firebase Firestore database).
 
 Open `http://localhost:3000` with your browser to see the result. The local data will be seeded from scratch. Furthermore, you can use the local auth service by simply logging in via any of the provided services (e.g., Google) with auto-generated credentials, which will simulate a logged in user account.

__seed__/README.md

@@ -21,12 +21,12 @@ reviewsData
 usersData
   /{userId}: <User>
 ```
-> ![NOTE]
+> [!NOTE]
 > The canonical path format for Firebase Firestore is `{collectionName}/{documentId}/{subCollectionName}/{subDocumentId}/...` and so on, with the path terminating at a (sub)document.
 
 ## Seeding a Firebase project
 
-> ![NOTE]
+> [!NOTE]
 > All paths indicated in this section are relative to the top-level directory (i.e., `website`). Furthermore, all commands (i.e., `yarn ...`) should also be issued from the top-level directory accordingly.
 
 ### Seeding or updating a cloud Firebase project
@@ -37,7 +37,7 @@ To seed the data in a development cloud-based Firebase Firestore database, defin
 yarn fb:seed-db-cloud
 ```
 
-> ![WARNING]
+> [!WARNING]
 > Do **NOT** use this method in **production**!!! Production Firebase database must be updated manually via the Firebase UI/console; otherwise, this seeding approach will wipe all of the live data **without** ability to recover it!
 
 ### Seeding or updating local *Firebase Emulator Suite*
@@ -81,7 +81,7 @@ This will update the corresponding files in directory `/__seed__/firebase-seed`.
 
 ## Adding a new course
 
-> ![NOTE]
+> [!NOTE]
 > All paths indicated here are relative to the top-level directory (i.e., `website`).
 
 To add a new course, update the following files:

firebase/README.md

@@ -2,10 +2,10 @@
 
 ## Preliminaries
 
-> ![NOTE]
+> [!NOTE]
 > All file-path references assume a starting point of the root directory of the project unless noted otherwise.
 
-> ![NOTE]
+> [!NOTE]
 > Requires Node v. 20+.
 
 ## Overview
@@ -48,7 +48,7 @@ The data documents defined in this app, and their corresponding CRUD operations'
 |  `Review`  | `getReviews(courseId, year, semesterTerm)` | `getReview(reviewId)` | `addReview(userId, reviewId, data)` | `updateReview(userId, reviewId, data)` | `deleteReview(userId, reviewId)` |
 |   `User`   |                   (N/A)                    |     `getUser(id)`     |            `addUser(id)`            |            `updateUser(id)`            |         `deleteUser(id)`         |
 
-> ![NOTE]
+> [!NOTE]
 > See `/globals/types.ts` for definition of document data fields (i.e., argument `data` per above).
 
 Example usage via `courses` document (and similarly for the others):
@@ -98,5 +98,5 @@ await updateCourse(courseId, updatedCourseData)
 await deleteCourse(courseId)
 ```
 
-> ![NOTE]
+> [!NOTE]
 > All non-"`GET`" operations require authorization/authentication via Firebase Authentication and corresponding permissions.

functions/README.md

@@ -6,7 +6,7 @@ This sub-repo contains the definitions for the Firebase Cloud Functions, intende
 
 ### Cloud Firebase Project
 
-> ![WARNING]
+> [!WARNING]
 > Deploying Cloud Functions requires a ***paid plan*** Firebase project, which must be preconfigured as such accordingly prior to deployment.
 
 To deploy the cloud functions as defined in `/website/functions/index.js` to a cloud-based Firebase project, ensure that the terminal is in location `.../website/functions/` and then perform the following steps via terminal: