Update community meeting cadence to biweekly (#2626)

Fix location of large-bundle-support.md

Signed-off-by: Todd Short <tshort@redhat.com>

Author: tmshort

docs/draft/concepts/clusterobjectsets.md

@@ -149,7 +149,7 @@ When operator-controller creates ClusterObjectSets for ClusterExtensions, it aut
 - Objects larger than 900 KiB are gzip-compressed before storage (ref resolution auto-detects and transparently decompresses gzip-compressed values so consumers see the original JSON manifest)
 - Content-addressable naming (based on SHA-256 hashes of the data) ensures that Secret names and data keys are deterministic, making creation idempotent and safe to retry
 
-For a detailed design discussion, see [Large Bundle Support](../../concepts/large-bundle-support.md).
+For a detailed design discussion, see [Large Bundle Support](large-bundle-support.md).
 
 ## Status conditions
 
@@ -390,4 +390,4 @@ Example output:
 NAME                   AVAILABLE   PROGRESSING   AGE
 my-extension-abc12     Unknown     False         2d
 my-extension-def34     True        True          1h
-```
+```

docs/project/olmv1_community.md

@@ -10,6 +10,6 @@ You can reach out to the OLM community for feedbacks/discussions/contributions i
 
 * Kubernetes Slack channel: [#olm-dev](https://kubernetes.slack.com/messages/olm-dev)
 * [Operator Framework on Google Groups](https://groups.google.com/forum/#!forum/operator-framework)
-* Weekly in-person Working Group meeting: [olm-wg](https://github.com/operator-framework/community#operator-lifecycle-manager-working-group)
+* Biweekly (every two weeks) in-person Working Group meeting: [olm-wg](https://github.com/operator-framework/community#operator-lifecycle-manager-working-group)
 
-For further information on contributing, please consult the [Contribution Guide](../contribute/contributing.md)
+For further information on contributing, please consult the [Contribution Guide](../contribute/contributing.md)