Merge pull request #1 from qlik-oss/doc_typo

Doc typo
qlik-oss · Jun 26, 2017 · b133e53 · b133e53
2 parents d52fbf4 + 5d8a3dd
commit b133e53
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
@@ -70,7 +70,7 @@ git push -u myfork my-feature-or-bugfix
 
 Before creating a Pull Request, make sure the following items are satisfied:
 
-- CircleCI is green (OBS!! This does not work with SSE yet right?)
+- CircleCI is green
 - Commit message format is followed
 - [CLA](#cla) is signed
 

diff --git a/docs/writing_a_plugin.md b/docs/writing_a_plugin.md
@@ -85,7 +85,7 @@ When the client (i.e., Qlik Sense) calls the RPC method `GetCapabilities`, the p
 When a function call is made from the UI, the engine calls the `ExecuteFunction` RPC method in your plugin. This method must delegate the call to the correct implementation of your functions. In the Python examples, we use the `getattr()` method and a dictionary that maps the function ID (which is sent in the request header) to the implemented function name. For more information, see [Writing an SSE plugin using Python](../examples/python/README.md).
 
 ## Cache control
-The default behavior of the Qlik engine is to cache results from computations in order to reduce the workload and speed up response time. This is valid as well for computations performed by SSE plugins. For some cases caching might be undesirable and it is possible to toggle it off per request. When `EvaluateScript` or `ExecuteFunction` are called the http header key:value pair `qlik-cache:no-cache` can be set in either the initial or trailing header data of the response. This functionality is demonstrated in the [Hello world example](../examples/python/HelloWorld/README.md#nocache-function).
+The default behavior of the Qlik engine is to cache results from computations in order to reduce the workload and speed up response time. This is valid as well for computations performed by SSE plugins. For some cases caching might be undesirable and it is possible to toggle it off per request. When `EvaluateScript` or `ExecuteFunction` are called the http header key:value pair `qlik-cache:no-store` can be set in either the initial or trailing header data of the response. This functionality is demonstrated in the [Hello world example](../examples/python/HelloWorld/README.md#nocache-function).
 
 Caching is automatically turned off as well if a request fails due to the communication failure or an exception is raised during a call.