From 6912c3db95b4ca0d78b5c388daae262321645624 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn-Egil=20Dahlberg?= <egil@erlang.org>
Date: Fri, 20 Jan 2017 14:12:18 +0100
Subject: otp: Don't mention percept in documentation

---
 system/doc/efficiency_guide/processes.xml | 4 ----
 1 file changed, 4 deletions(-)

(limited to 'system/doc/efficiency_guide/processes.xml')

diff --git a/system/doc/efficiency_guide/processes.xml b/system/doc/efficiency_guide/processes.xml
index f2d9712f51..b9982353be 100644
--- a/system/doc/efficiency_guide/processes.xml
+++ b/system/doc/efficiency_guide/processes.xml
@@ -261,10 +261,6 @@ true
     The estone benchmark, for example, is entirely sequential. So is
     the most common implementation of the "ring benchmark"; usually one process
     is active, while the others wait in a <c>receive</c> statement.</p>
-
-    <p>The <seealso marker="percept:percept">percept</seealso> application
-    can be used to profile your application to see how much potential (or lack
-    thereof) it has for concurrency.</p>
   </section>
 </chapter>
 
-- 
cgit v1.2.3