a

docs/README.md

@@ -368,7 +368,7 @@ main()
 
 ## Feature Compatibility
 
-This table provides an overview of the features that Token.js supports from each LLM provider. If an LLM provider does not support a certain feature, it is marked with a dash (:heavy_minus_sign:) in the table.
+This table provides an overview of the features that Token.js supports from each LLM provider.
 
 | Provider   | Chat Completion           | Streaming            | Tools                | JSON Output          | Image Input          |
 | ---------- | -------------------- | -------------------- | -------------------- | -------------------- | -------------------- |
@@ -382,7 +382,11 @@ This table provides an overview of the features that Token.js supports from each
 | Groq       | :white\_check\_mark: | :white\_check\_mark: |  :heavy_minus_sign:  | :white\_check\_mark: |  :heavy_minus_sign:  |
 | Perplexity | :white\_check\_mark: | :white\_check\_mark: |  :heavy_minus_sign:  |  :heavy_minus_sign:  |  :heavy_minus_sign:  |
 
-Certain LLMs, particularly older or weaker models, do not support some features in this table. For details about these restrictions, see our [LLM provider documentation](providers/README.md).
+#### Key
+:white\_check\_mark: Supported by Token.js
+:heavy_minus_sign: Not supported by the LLM provider
+
+**Note**: Certain LLMs, particularly older or weaker models, do not support some features in this table. For details about these restrictions, see our [LLM provider documentation](providers/README.md).
 
 ## License
 
@@ -391,4 +395,7 @@ Token.js is free and open source software licensed under [GPLv3](https://github.
 
 TODO(later): actually run the example code to make sure you get a valid response for each provider. (finished readme)
 TODO(later): be consistent with casing for token.js. (finished readme)
-TODO(later): grammarly (finished readme)
+TODO(later): grammarly (finished readme)
+TODO: I think users may find it confusing that we link to the provider's documentation in its current form, particularly because we don't supply our own docs. I'm concerned users will think that they should go to the provider's page to learn about their fields. Is there a reason for us to link to their docs at all? Perhaps to get an API key.
+TODO(later): update repo readme.
+TODO: make an API reference page.