Add Vale PR check back in

.github/workflows/vale.yml

@@ -0,0 +1,38 @@
+name: Vale style check
+on: 
+  pull_request:
+    paths:
+      - '**.mdx'
+      - '**.md'
+      - '.vale/**'
+      - '.vale.ini'
+      - '!**/changelog/**'
+
+jobs:
+  vale:
+    runs-on: ubuntu-latest
+    if: |
+      github.event.pull_request.user.login != 'fern-support' &&
+      github.event.pull_request.user.login != 'github-actions'
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Get changed files
+        id: changed-files
+        uses: tj-actions/changed-files@v41
+        with:
+          files: |
+            fern/**/*.md
+            fern/**/*.mdx
+          files_ignore: |
+            **/changelog/**
+
+      - uses: errata-ai/vale-action@reviewdog
+        if: steps.changed-files.outputs.any_changed == 'true'
+        with:
+          files: ${{ steps.changed-files.outputs.all_changed_files }}
+          version: 3.12.0
+          reporter: github-pr-review
+          fail_on_error: false
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

fern/products/docs/pages/api-references/audiences.mdx

@@ -5,6 +5,7 @@ subtitle: Use audiences to filter the endpoints, schemas, and properties that ar
 
 <Markdown src="/snippets/pro-plan.mdx"/>
 
+test change please please check
 Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include `public` 
 and `beta`. You can configure audiences in both [the OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences) as well as [the Fern Definition](/learn/api-definition/fern/audiences).