changeset 49403:fdf3f14be8b2

8199561: Fix two typos in the JVMTI documentation Summary: Fix two typos in the JVMTI documentation Reviewed-by: sspitsyn, dholmes Contributed-by: jcbeyler@google.com
author jcbeyler
date Wed, 14 Mar 2018 09:58:53 -0700
parents d3a8aa01f26f
children e0fec3292f00
files src/hotspot/share/prims/jvmti.xml
diffstat 1 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/src/hotspot/share/prims/jvmti.xml	Wed Mar 14 09:09:38 2018 -0700
+++ b/src/hotspot/share/prims/jvmti.xml	Wed Mar 14 09:58:53 2018 -0700
@@ -693,7 +693,7 @@
     mechanism causes the unload (an unload mechanism is not specified in this document)
     or the library is (in effect) unloaded by the termination of the VM whether through
     normal termination or VM failure, including start-up failure.
-    Uncontrolled shutdown is, of couse, an exception to this rule.
+    Uncontrolled shutdown is, of course, an exception to this rule.
     Note the distinction between this function and the
     <eventlink id="VMDeath">VM Death event</eventlink>: for the VM Death event
     to be sent, the VM must have run at least to the point of initialization and a valid
@@ -9405,7 +9405,7 @@
 	    the event <paramlink id="event_type"></paramlink> will be disabled
 	  </constant>
 	</constants>
-	If <code>thread</code> is <code>NULL</code>,
+	If <code>event_thread</code> is <code>NULL</code>,
 	the event is enabled or disabled globally; otherwise, it is
 	enabled or disabled for a particular thread.
 	An event is generated for