Update README.md to remove "Feature Flags" after "Harness"

As written, someone could think that this has something to do with FF Classic.  Just removed the phrase "Feature Flags" after the word Harness so that won't happen.

Author: dtk-DaveKarow

README.md

@@ -8,7 +8,7 @@ Full documentation on this Python wrapper is available in [this link](https://he
 
 ## Using in Harness Mode
 
-Starting with version 3.5.0, the Split API client supports operating in "harness mode" to interact with both Split and Harness Feature Flags APIs. This is required for usage in environments that have been migrated to Harness and want to use the new features. Existing API keys will continue to work with the non-deprecated endpoints after migration, but new Harness Tokens will be required for Harness mode.
+Starting with version 3.5.0, the Split API client supports operating in "harness mode" to interact with both Split and Harness APIs. This is required for usage in environments that have been migrated to Harness and want to use the new features. Existing API keys will continue to work with the non-deprecated endpoints after migration, but new Harness Tokens will be required for Harness mode.
 
 For detailed information about Harness API endpoints, please refer to the [official Harness API documentation](https://apidocs.harness.io/).
 
@@ -395,4 +395,4 @@ Visit [split.io/product](https://www.split.io/product) for an overview of Split,
 
 **System Status:**
 
-We use a status page to monitor the availability of Split's various services. You can check the current status at [status.split.io](http://status.split.io).
+We use a status page to monitor the availability of Split's various services. You can check the current status at [status.split.io](http://status.split.io).