chore: ignore bug fixes in readme during linting (#876)

.github/linters/.textlintrc

@@ -0,0 +1,10 @@
+{
+  "filters": {
+    "comments": true
+  },
+  "rules": {
+    "terminology" : {
+      "defaultTerms": true
+    }
+  }
+}

.github/workflows/lint.yml

@@ -23,5 +23,6 @@ jobs:
           VALIDATE_POWERSHELL: false
           VALIDATE_EDITORCONFIG: false
           VALIDATE_MARKDOWN: false
+          NATURAL_LANGUAGE_CONFIG_FILE: .textlintrc
           DEFAULT_BRANCH: main
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -79,9 +79,9 @@ You can find detailed usage documentation and code samples under [docs](/docs/RE
 We use a modified version of [Semantic Versioning](https://semver.org/) for all changes. See [version strategy](VERSIONS.md) for details which is effective from 30 July 2022.
 
 ### Supported Version
-
+<!-- textlint-disable -->
 Only the current MAJOR version of SDK is supported. New features, functionality, bug fixes, and security updates will only be added to the current MAJOR version.
-
+<!-- textlint-enable -->
 A current release is on the leading edge of our SDK development, and is intended for customers who are in active development and want the latest and greatest features.  Instead of stating a release date for a new feature, we set a fixed minor or patch release cadence of maximum 2-3 months (while we may release more often). At the same time, there is no schedule for major or breaking release. Instead, we will communicate one quarter in advance the upcoming breaking change to allow customers to plan for the upgrade. We always recommend that all users run the latest available minor release for whatever major version is in use. We highly recommend upgrading to the latest SDK major release at the earliest convenient time and before the EOL date.
 
 ### Version schedule