summaryrefslogtreecommitdiffstats
path: root/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc')
-rw-r--r--documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc3
1 files changed, 1 insertions, 2 deletions
diff --git a/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc b/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
index e9da228b1a..c9184be047 100644
--- a/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
+++ b/documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc
@@ -16,8 +16,7 @@ https://developers.google.com/analytics/devguides/collection/gajs/[Google
Analytics]. Because the Analytics API just uses the same `_gaq.push`
function with different arguments, the JavaScript connector logic can be
equally simple. Aside from asynchronously loading ga.js, the client-side
-code just adds a callback (see link:SimplifiedRPCusingJavaScript.asciidoc[Simplified RPC using JavaScript] for
-more information) that the server-side code can use to push new
+code just adds a callback that the server-side code can use to push new
commands.
[source,javascript]