Skip to content

Commit 6d7d4c6

Browse files
docs: update SDK compatibility link to new path (#349)
Changing a link in the `README.md` from `/technologies` to `/sdks` Signed-off-by: Jonathan Norris <[email protected]>
1 parent 4443c34 commit 6d7d4c6

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,15 +49,16 @@ The OpenFeature SDK provides a mechanism for interfacing
4949
with an external evaluation engine in a vendor agnostic way;
5050
it does **not** itself handle the flag evaluation logic.
5151

52-
An up-to-date SDK compatibility overview can be found [here](https://openfeature.dev/docs/reference/technologies/sdk-compatibility).
52+
An up-to-date SDK compatibility overview can be found [here](https://openfeature.dev/docs/reference/sdks/sdk-compatibility).
5353

5454
### Tooling
5555

5656
This specification complies with [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119) and seeks to conform to the [W3C QA Framework Guidelines](https://www.w3.org/TR/qaframe-spec/).
5757

5858
In accordance with this, some basic tooling (donated graciously by [Diego Hurtado](https://github.com/ocelotl)) has been employed to parse the specification and output a JSON structure of concise requirements, highlighting the particular `RFC 2119` verb in question.
5959

60-
To parse the specification, simply type `make`. Please review the generated JSON files, which will appear as siblings to any of the markdown files in the `/specification` folder.
60+
To parse the specification, simply type `make`.
61+
Please review the generated JSON files, which will appear as siblings to any of the markdown files in the `/specification` folder.
6162

6263
### Style Guide
6364

0 commit comments

Comments
 (0)