Update community meeting references to weekly

Co-authored-by: maelvls <[email protected]>

Author: Copilot

content/docs/contributing/README.md

@@ -21,7 +21,7 @@ you should receive calendar invites by mail shortly after joining. The complexit
 might be sent multiple times depending on your email and calendar providers and you might get some invites for past
 or future meetings which have been rescheduled or edited. Sorry about that!
 
-We have 2 regular repeating meetings: our quick daily check-in and an hour-long community meeting every two weeks.
+We have 2 regular repeating meetings: our quick daily check-in and the cert-manager weekly community meeting.
 
 If you're having any issues joining our meetings, ensure that you're part of the [`cert-manager-dev`](https://groups.google.com/forum/#!forum/cert-manager-dev) Google group, and always feel free to ask in [Slack](./#slack) for help!
 
@@ -49,7 +49,7 @@ We'll ensure that anyone outside of the core maintainer team who has a talking p
 
 ### Community Meetings
 
-Our bi-weekly (i.e. every two weeks) community meetings happen [on Zoom](https://zoom.us/j/96658445866) at [17:00 London time](http://www.thetimezoneconverter.com/?t=17:00&tz=Europe/London). You can look at the [CNCF calendar](https://tockify.com/cncf.public.events/monthly?search=cert-manager) to see when the next one will take place.
+The cert-manager weekly community meeting happens [on Zoom](https://zoom.us/j/96658445866) at [17:00 London time](http://www.thetimezoneconverter.com/?t=17:00&tz=Europe/London). You can look at the [CNCF calendar](https://tockify.com/cncf.public.events/monthly?search=cert-manager) to see when the next one will take place.
 
 These meetings are an hour-long chat about cert-manager topics. It's a great way to get involved with contributing for the
 first time; to get answers to any questions you might have; or to propose a new feature which needs some explanation.

content/docs/contributing/contributing-flow.md

@@ -145,7 +145,7 @@ When a milestone is set on an Issue it is generally an indication of when we pla
 Prow will apply milestones on merged PRs, this will tell you in which version that PR will land.
 
 The milestone page will also have an indicated due date when we will release. This might have some delay.
-We brief our users/contributors about this in our bi-weekly community meeting, for an up to date status report we recommend joining these.
+We brief our users/contributors about this in the cert-manager weekly community meeting, for an up to date status report we recommend joining these.
 
 ### Labels
 

content/docs/contributing/policy.md

@@ -36,7 +36,7 @@ Do reach out if you need help with the design.
 
 Part of the process of discussing a design document may also include a video call with you included! That helps us to plan how a feature should
 be implemented and approached. It'll be pretty informal and casual; we just want to make sure we're all on the same page. This call might be part
-of a biweekly meeting.
+of the cert-manager weekly community meeting.
 
 #### Making Progress with Larger Features
 
@@ -46,14 +46,14 @@ questions, but they should certainly be able to point you in the right direction
 
 To get in touch to discuss a feature, please reach out on the [cert-manager-dev slack channel](./README.md#slack), or join a [cert-manager public meeting](./README.md#meetings) to talk about your proposal.
 
-If you have an open PR with a design document (or have some questions about how to proceed with a design), you should absolutely feel free to add the PR with your design or a link to the relevant GitHub issue to the [meeting notes](https://docs.google.com/document/d/1Tc5t6ylY9dhXAan1OjOoldeaoys1Yh4Ir710ATfBa5U/edit) for our next biweekly meeting
+If you have an open PR with a design document (or have some questions about how to proceed with a design), you should absolutely feel free to add the PR with your design or a link to the relevant GitHub issue to the [meeting notes](https://docs.google.com/document/d/1Tc5t6ylY9dhXAan1OjOoldeaoys1Yh4Ir710ATfBa5U/edit) for the cert-manager weekly community meeting
 and join in so we're sure to discuss it and so you can contribute to the discussion!
 
 #### Large Feature Lifecycle
 
 1. Informally ask about the feature in slack or a public meeting
 2. Create a PR with a lightweight design document using the [design template](https://github.com/cert-manager/cert-manager/tree/master/design/template.md), for discussion
-3. Design doc PR gets reviewed - possibly includes meeting or discussion in a biweekly meeting
+3. Design doc PR gets reviewed - possibly includes meeting or discussion in the cert-manager weekly community meeting
 4. Implement your feature, helped and reviewed by a named cert-manager maintainer
 
 ## Feature Requests We'll Likely Reject
@@ -63,7 +63,7 @@ In some cases, people will request features which we've previously rejected or w
 It's nothing personal; sometimes we have to make tough choices and especially when it comes to security and maintainability we have to reject certain
 proposals. If your feature request is listed below, there's a high chance we'll have to reject it.
 
-That said, if you think we've made a mistake and that we should reconsider, we're open to chatting - consider joining our [biweekly meetings](./README.md#meetings) to discuss it with us!
+That said, if you think we've made a mistake and that we should reconsider, we're open to chatting - consider joining the cert-manager weekly community meeting to discuss it with us!
 
 ### Vendoring Kubernetes related APIs outside of the `k8s.io/` namespace