Updated RFCs and meetings notes in accordance to 11-08-2022 meeting

Signed-off-by: chanmosq <[email protected]>

meetings/README.md

@@ -23,7 +23,7 @@ O3DE cannot work without the help and input from as many of its community member
 | 2022-09-13 | [Link](https://github.com/o3de/sig-docs-community/issues/60) | N/A  |
 | 2022-09-27 | [Link](https://github.com/o3de/sig-docs-community/issues/63) | [On Agenda](https://github.com/o3de/sig-docs-community/issues/63#issuecomment-1259931430) |
 | 2022-10-18 | [Link](https://github.com/o3de/sig-docs-community/issues/66) | [On Agenda](https://github.com/o3de/sig-docs-community/issues/66#issuecomment-1286035611) |
-
+| 2022-11-08 | [Link](https://github.com/o3de/sig-docs-community/issues/68) | [On Agenda](https://github.com/o3de/sig-docs-community/issues/68#issuecomment-1307737835) |
 
 
 ## Pre-release meetings

rfcs/README.md

@@ -23,3 +23,5 @@ This section is a running list of RFCs that have been accepted by the SIG.
 |-----|---------|
 | https://github.com/o3de/sig-docs-community/issues/32 | Separate `main` and `development` branches of o3de.org to reflect different product states and to prepare for website versioning. |
 | https://github.com/o3de/sig-docs-community/issues/8 | Accepting SIG charter. |
+| https://github.com/o3de/sig-docs-community/issues/64 | Documentation health in each important feature area needs to be reported in some way for the O3DE feature grid. This RFC covers the column extensions and terminology used by sig-docs-community for reporting on the state of documentation in a way that aligns with how SIGs report on the state of their features to the TSC, TAC, and Governing Board. |
+| https://github.com/o3de/sig-docs-community/issues/61 | This RFC is to establish a system where we can separate out different maintainers and owners of the o3de.org website. |