Github user davebarnes97 commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/64#discussion_r107042429
--- Diff:
docs/geode-native-docs/continuous-querying/3-native-client-cq-api.html.md.erb
---
@@ -21,9 +21,10 @@ limitations under the License.
This chapter documents the primary native client API for CQ management.
-The Apache Geode native client API allows your clients to create and
manage CQs. (The server side does not have an API.) Continuous querying
provides native client query syntax, events-based management, integration with
client/server architecture, active query execution, and interest criteria based
on data values. For complete information on the classes and interfaces
described here, see the API documentation at
[http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+The Apache Geode native client API allows your clients to create and
manage CQs. (The server side does not have an API.) Continuous querying
provides native client query syntax, events-based management, integration with
client/server architecture, active query execution, and interest criteria based
on data values. For complete information on the classes and interfaces
described here,
+see the API documentation for [C++](/releases/latest/api/cppdocs) or
[C\#](/releases/latest/api/dotnetdocs).
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Client.Cache**
--- End diff --
The preceding text says it will be using C# notation, so it should have
been C# all along.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
