diff --git a/website/docs/advanced/code-references/bitbucket-pipe.mdx b/website/docs/advanced/code-references/bitbucket-pipe.mdx index b5d380ab..228980aa 100644 --- a/website/docs/advanced/code-references/bitbucket-pipe.mdx +++ b/website/docs/advanced/code-references/bitbucket-pipe.mdx @@ -10,7 +10,7 @@ You can find more information about Bitbucket Pipelines ConfigCat Management API credential and store its values in secure pipeline variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - Bitbucket Pipe secrets + Bitbucket Pipe secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/advanced/code-references/bitrise-step.mdx b/website/docs/advanced/code-references/bitrise-step.mdx index a78685d1..b79bb990 100644 --- a/website/docs/advanced/code-references/bitrise-step.mdx +++ b/website/docs/advanced/code-references/bitrise-step.mdx @@ -10,7 +10,7 @@ to automatically scan your source code for feature flag and setting usages and u ## Setup 1. Create a new ConfigCat Management API credential and store its values in secure pipeline variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - Bitrise secrets + Bitrise secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/advanced/code-references/circleci-orb.mdx b/website/docs/advanced/code-references/circleci-orb.mdx index 3acd041a..bec284a3 100644 --- a/website/docs/advanced/code-references/circleci-orb.mdx +++ b/website/docs/advanced/code-references/circleci-orb.mdx @@ -10,7 +10,7 @@ You can find more information about CircleCI Orbs ConfigCat Management API credential and store its values in CircleCI Environment Variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - CircleCI Orb secrets + CircleCI Orb secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/integrations/amplitude.mdx b/website/docs/integrations/amplitude.mdx index 3776481d..cdeb26eb 100644 --- a/website/docs/integrations/amplitude.mdx +++ b/website/docs/integrations/amplitude.mdx @@ -18,7 +18,7 @@ There are two available integration opportunities between ConfigCat and Amplitud Every feature flag change in ConfigCat is annotated on the Amplitude charts as a vertical line and some details are added automatically about the change. -amplitude_chart +amplitude_chart ### Installation @@ -41,7 +41,7 @@ Every annotation sent to Amplitude by ConfigCat has: - **Name:** A brief summary of the change. - **Description:** A direct link to the Product/Config/Environment of the feature flag in ConfigCat. -amplitude_annoation +amplitude_annoation ## Sending feature flag evaluation analytics to Amplitude Experiments {#experiments} @@ -260,8 +260,8 @@ Check your Experiments page in Amplitude and select your feature flag as the Exp ### Usage with custom chart If you don't have access to the Experiments feature in Amplitude, you can create a custom chart based on the `Exposure` event. You can filter for your feature flag keys with the `Flag Key` property and visualize the different variants by using the `Variant` property as a Breakdown. Example: -Amplitude custom chart +Amplitude custom chart ### Usage with enriched user properties for your custom events. If you use the Identify API approach, you'll be able to use the feature flag evaluation data in your current reports. You can Group Segments by your feature flag evaluations: -Amplitude chart with enriched data \ No newline at end of file +Amplitude chart with enriched data \ No newline at end of file diff --git a/website/docs/integrations/jira.mdx b/website/docs/integrations/jira.mdx index 21fc7f27..3826b500 100644 --- a/website/docs/integrations/jira.mdx +++ b/website/docs/integrations/jira.mdx @@ -8,7 +8,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Installation of the ConfigCat Feature Flags Jira Cloud Plugin 1. Add ConfigCat Feature Flags to your Jira Cloud instance. 2. Select `Configure`. @@ -21,7 +21,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Linking existing feature flags in Jira Cloud Plugin 1. Open any Issue on your Jira board. 2. Push `Link/Create ConfigCat Feature Flag` @@ -30,7 +30,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Create feature flags in Jira Cloud Plugin 1. Open any Issue on your Jira board. 2. Push `Link/Create ConfigCat Feature Flag` @@ -41,7 +41,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +View and Edit linked feature flags in Jira Cloud Plugin 1. Open an Issue on your Jira board with linked feature flag. 2. You can see the linked feature flags in the `Feature Flag (ConfigCat)` issue section. @@ -52,26 +52,26 @@ Turn features On / Off right from a linked Issue on your Jira board with +Remove linked feature flags in Jira Cloud Plugin 1. Open an Issue on your Jira board with linked feature flag. 2. Remove the linked feature flag by clicking the red X in the top right corner. ### View flag status in Releases -View feature flags in releases field +View feature flags in releases field 1. Open an Issue on your Jira board with linked feature flag. 2. Check the `Releases` field values in the issue Details section to see the linked feature flags status in the Issue. 3. Click it for more detailed dialog. -View feature flags in Release hub +View feature flags in Release hub 1. Open a version in the project Release Hub to see the related issues feature flag status. 2. Click it for more detailed dialog. ### View linked issues in ConfigCat -Link in Dashboard +Link in Dashboard 1. View linked issues next to your Feature Flags in ConfigCat and jump to the Jira Issue directly. diff --git a/website/docs/integrations/segment.mdx b/website/docs/integrations/segment.mdx index 37e0488f..6c4038c5 100644 --- a/website/docs/integrations/segment.mdx +++ b/website/docs/integrations/segment.mdx @@ -18,7 +18,7 @@ There are two available integration opportunities between [ConfigCat and Twilio Ensures that every setting change in ConfigCat is sent to Segment as a track event. -Twilio Segment Feature Flag Changed event +Twilio Segment Feature Flag Changed event ### Installation @@ -429,4 +429,4 @@ The `variationId` is a hashed version of the feature flag value, accessible on t ### Example event Check your source's debugger to see the events. -Twilio Segment event debugger +Twilio Segment event debugger diff --git a/website/docs/integrations/zapier.mdx b/website/docs/integrations/zapier.mdx index 7e576972..f4488928 100644 --- a/website/docs/integrations/zapier.mdx +++ b/website/docs/integrations/zapier.mdx @@ -29,7 +29,7 @@ Each Zap has one app as the **Trigger**, where your information comes from and w 1. You should select the [Product](../main-concepts.mdx#product) in which you want to get notified about the Feature Flag or Setting value changes and optionally you can filter these notifications by specific [Configs](../main-concepts.mdx#config) or [Environments](../main-concepts.mdx#environment). -zapier_customize +zapier_customize 1. Once that's done you can start creating an automation! Use a pre-made Zap or create your own with the Zap Editor. Creating a Zap requires no coding knowledge and you'll be walked step-by-step through the setup. @@ -48,7 +48,7 @@ Available fields to include in your flow: ### Configuration in Zapier -zapier_config +zapier_config ### Result in Slack diff --git a/website/versioned_docs/version-V1/integrations/amplitude.mdx b/website/versioned_docs/version-V1/integrations/amplitude.mdx index 3776481d..cdeb26eb 100644 --- a/website/versioned_docs/version-V1/integrations/amplitude.mdx +++ b/website/versioned_docs/version-V1/integrations/amplitude.mdx @@ -18,7 +18,7 @@ There are two available integration opportunities between ConfigCat and Amplitud Every feature flag change in ConfigCat is annotated on the Amplitude charts as a vertical line and some details are added automatically about the change. -amplitude_chart +amplitude_chart ### Installation @@ -41,7 +41,7 @@ Every annotation sent to Amplitude by ConfigCat has: - **Name:** A brief summary of the change. - **Description:** A direct link to the Product/Config/Environment of the feature flag in ConfigCat. -amplitude_annoation +amplitude_annoation ## Sending feature flag evaluation analytics to Amplitude Experiments {#experiments} @@ -260,8 +260,8 @@ Check your Experiments page in Amplitude and select your feature flag as the Exp ### Usage with custom chart If you don't have access to the Experiments feature in Amplitude, you can create a custom chart based on the `Exposure` event. You can filter for your feature flag keys with the `Flag Key` property and visualize the different variants by using the `Variant` property as a Breakdown. Example: -Amplitude custom chart +Amplitude custom chart ### Usage with enriched user properties for your custom events. If you use the Identify API approach, you'll be able to use the feature flag evaluation data in your current reports. You can Group Segments by your feature flag evaluations: -Amplitude chart with enriched data \ No newline at end of file +Amplitude chart with enriched data \ No newline at end of file diff --git a/website/versioned_docs/version-V1/integrations/jira.mdx b/website/versioned_docs/version-V1/integrations/jira.mdx index 21fc7f27..3826b500 100644 --- a/website/versioned_docs/version-V1/integrations/jira.mdx +++ b/website/versioned_docs/version-V1/integrations/jira.mdx @@ -8,7 +8,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Installation of the ConfigCat Feature Flags Jira Cloud Plugin 1. Add ConfigCat Feature Flags to your Jira Cloud instance. 2. Select `Configure`. @@ -21,7 +21,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Linking existing feature flags in Jira Cloud Plugin 1. Open any Issue on your Jira board. 2. Push `Link/Create ConfigCat Feature Flag` @@ -30,7 +30,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +Create feature flags in Jira Cloud Plugin 1. Open any Issue on your Jira board. 2. Push `Link/Create ConfigCat Feature Flag` @@ -41,7 +41,7 @@ Turn features On / Off right from a linked Issue on your Jira board with +View and Edit linked feature flags in Jira Cloud Plugin 1. Open an Issue on your Jira board with linked feature flag. 2. You can see the linked feature flags in the `Feature Flag (ConfigCat)` issue section. @@ -52,26 +52,26 @@ Turn features On / Off right from a linked Issue on your Jira board with +Remove linked feature flags in Jira Cloud Plugin 1. Open an Issue on your Jira board with linked feature flag. 2. Remove the linked feature flag by clicking the red X in the top right corner. ### View flag status in Releases -View feature flags in releases field +View feature flags in releases field 1. Open an Issue on your Jira board with linked feature flag. 2. Check the `Releases` field values in the issue Details section to see the linked feature flags status in the Issue. 3. Click it for more detailed dialog. -View feature flags in Release hub +View feature flags in Release hub 1. Open a version in the project Release Hub to see the related issues feature flag status. 2. Click it for more detailed dialog. ### View linked issues in ConfigCat -Link in Dashboard +Link in Dashboard 1. View linked issues next to your Feature Flags in ConfigCat and jump to the Jira Issue directly. diff --git a/website/versioned_docs/version-V1/integrations/segment.mdx b/website/versioned_docs/version-V1/integrations/segment.mdx index 37e0488f..6c4038c5 100644 --- a/website/versioned_docs/version-V1/integrations/segment.mdx +++ b/website/versioned_docs/version-V1/integrations/segment.mdx @@ -18,7 +18,7 @@ There are two available integration opportunities between [ConfigCat and Twilio Ensures that every setting change in ConfigCat is sent to Segment as a track event. -Twilio Segment Feature Flag Changed event +Twilio Segment Feature Flag Changed event ### Installation @@ -429,4 +429,4 @@ The `variationId` is a hashed version of the feature flag value, accessible on t ### Example event Check your source's debugger to see the events. -Twilio Segment event debugger +Twilio Segment event debugger diff --git a/website/versioned_docs/version-V1/integrations/zapier.mdx b/website/versioned_docs/version-V1/integrations/zapier.mdx index 7e576972..335e4be6 100644 --- a/website/versioned_docs/version-V1/integrations/zapier.mdx +++ b/website/versioned_docs/version-V1/integrations/zapier.mdx @@ -29,7 +29,7 @@ Each Zap has one app as the **Trigger**, where your information comes from and w 1. You should select the [Product](../main-concepts.mdx#product) in which you want to get notified about the Feature Flag or Setting value changes and optionally you can filter these notifications by specific [Configs](../main-concepts.mdx#config) or [Environments](../main-concepts.mdx#environment). -zapier_customize +zapier_customize 1. Once that's done you can start creating an automation! Use a pre-made Zap or create your own with the Zap Editor. Creating a Zap requires no coding knowledge and you'll be walked step-by-step through the setup. @@ -48,11 +48,11 @@ Available fields to include in your flow: ### Configuration in Zapier -zapier_config +zapier_config ### Result in Slack -zapier_slack +zapier_slack ## Need help?