convert OSS language to "community" (#22343)

website/content/api-docs/relatedtools.mdx

@@ -34,7 +34,7 @@ The following list of tools is maintained by the community of Vault users; Hashi
 - [vsh](https://github.com/fishi0x01/vsh) - Interactive shell with tab-completion. Allows recursive operations on paths. Allows migration of secrets between both KV versions.
 - [vault-cli](https://github.com/IBM/vault-cli) - A yaml based automation tool that bootstraps Vault cluster(s) with the desired configuration (namespaces, endpoints, policies, roles, endpoint)
 - [vault-go](https://github.com/IBM/vault-go) - Helper Golang Vault types as Kubernetes Custom Resource Definitions (CRD)
-- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate highly-available cloud with Consul, Nomad, Vault, and optional support for Waypoint. OSS & Enterprise supported.
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate highly-available cloud with Consul, Nomad, Vault, and optional support for Waypoint. Community & Enterprise supported.
 - [vkv](https://github.com/FalcoSuessgott/vkv) - Recursively list key-values entries from Vaults KV2 engine in various formats.
 
 Want to add your own project, or one that you use? Additions are welcome via [pull requests](https://github.com/hashicorp/vault/blob/main/website/content/api-docs/relatedtools.mdx).

website/content/api-docs/secret/identity/mfa/index.mdx

@@ -22,6 +22,6 @@ description: >-
 - [Login Enforcement](/vault/api-docs/secret/identity/mfa/login-enforcement)
 - [MFA Validate](/vault/api-docs/system/mfa/validate)
 
-While the above endpoints are available in both the open source and Enterprise versions of Vault,
+While the above endpoints are available in all editions of Vault,
 they are namespace aware. MFA methods and login enforcements created in one namespace are separate from other
-namespaces. In the open source version of Vault, everything operates in the root namespace.
+namespaces. In the community version of Vault, everything operates in the root namespace.

website/content/api-docs/secret/pki.mdx

@@ -4099,7 +4099,7 @@ the CRL.
 
 ~> Note: The `unified_crl`, `unified_crl_on_existing_paths`, and
    `cross_cluster_revocation` parameters are all Vault Enterprise only
-   functionality. While they appear in the responses on Vault OSS, they cannot
+   functionality. While they appear in the responses on Vault Community Edition, they cannot
    be enabled.
 
 | Method | Path              |

website/content/api-docs/system/internal-counters.mdx

@@ -873,7 +873,7 @@ The `/sys/internal/counters/config` endpoint is used to configure logging of act
 
 - `default_report_months` `(integer: 12)` - The number of months to report if no `start_time` is specified in a query.
 - `enabled` `(string: enable, disable, default)` - Enable or disable counting of client activity. When set to `default`, the client
-  counts are enabled on Enterprise builds and disabled on OSS builds. Disabling the feature during the middle of a month will
+  counts are enabled on Enterprise builds and disabled on community builds. Disabling the feature during the middle of a month will
   discard any data recorded for that month, but does not delete previous months.
 - `retention_months` `(integer: 24)` - The number of months of history to retain.
 

website/content/api-docs/system/mfa/index.mdx

@@ -31,7 +31,7 @@ returns an ID when a method is created. Although MFA methods supported with Step
 - Step-up Enterprise MFA: `sys/mfa/method/:type/:/name`
 - Login MFA: `identity/mfa/method/:type`
 
-~> **Note:** While the `sys/mfa` endpoint is supported for both OSS and Vault Enterprise, `sys/mfa/method/:type/:/name` is only supported for Vault Enterprise.
+~> **Note:** While the `sys/mfa` endpoint is supported for both Vault Community and Enterprise editions, `sys/mfa/method/:type/:/name` is only supported for Vault Enterprise.
 
 Refer to the [Login MFA
 FAQ](/vault/docs/auth/login-mfa/faq#q-are-there-new-mfa-api-endpoints-introduced-as-part-of-the-new-vault-version-1-10-mfa-for-login-functionality) document