Fixing typos, fix broken link (#51)

docs/content/_index.html

@@ -27,7 +27,7 @@
 {{% /blocks/feature %}}
 
 {{% blocks/feature icon="fas fa-search" title="Java Mission Control" url="docs/jmc" %}}
-Learn how to levarage Java Mission Control with Flight Recorder to get insight into your running application.
+Learn how to leverage Java Mission Control with Flight Recorder to get insight into your running application.
 {{% /blocks/feature %}}
 
 {{% blocks/feature icon="fas fa-memory" title="Memory Analysis" url="docs/memory" %}}

docs/content/docs/containers/java_monitoring.md

@@ -32,7 +32,7 @@ We'll set the following properties as a `JAVA_OPTS` environment variable when we
 * Disabling for both the registry and jmx: `-Dcom.sun.management.jmxremote.registry.ssl=false` and `-Dcom.sun.management.jmxremote.ssl=false`
 * Accept connections not from localhost: `-Dcom.sun.management.jmxremote.local.only=false`
   * Since the machine we are connecting from will not be in the container network, we need to allow non localhost connections.
-* The host name for the [RMI server](https://docs.oracle.com/javase/8/docs/technotes/guides/rmi/javarmiproperties.html) will be set to `127.0.0.1`. The default value for this will be the container's IP address, which we are overridding.
+* The host name for the [RMI server](https://docs.oracle.com/javase/8/docs/technotes/guides/rmi/javarmiproperties.html) will be set to `127.0.0.1`. The default value for this will be the container's IP address, which we are overriding.
 
 Set these values as an `environment` property on your workshop container:
 

docs/content/docs/intro/_index.md

@@ -104,7 +104,7 @@ There's a couple of java utilities that can also be used to find the PIDs of you
 
 ### jps
 
-The [Java Virtual Machine Process Status Tool](https://docs.oracle.com/javase/7/docs/technotes/tools/share/jps.html) can be used to see Java processess.
+The [Java Virtual Machine Process Status Tool](https://docs.oracle.com/javase/7/docs/technotes/tools/share/jps.html) can be used to see Java processes.
 
 ```bash
  $ jps

docs/content/docs/jmc/_intro_jmc7.md

@@ -202,7 +202,7 @@ From a Java Flight Recording, there are several categories of information (pages
   * __Socket I/O__: Displays Network costs and behaviors
 * JVM Internals:
   * __Garbage Collections__: Displays heap usage compared to pause times as well as GC events.
-  * __Compliations__: Provides details on code compilation.
+  * __Compilations__: Provides details on code compilation.
   * __TLAB Allocations__: Displays Thread Local Allocation Buffers.
 * System Information:
   * __Processes__: See other processes on the system and what is competing for resources.
@@ -212,7 +212,7 @@ From a Java Flight Recording, there are several categories of information (pages
   __Event Browser__: View detailed log of the events within the JVM. You can use this page to further filter down on events across all the pages in the recording.
 
 {{% alert title="Note" color="info" %}}
-Feel free to reference the additional [resources](/docs/jmc/references) as you navigate through the sections.
+Feel free to reference the additional [resources](/docs/jmc/_references/) as you navigate through the sections.
 {{% /alert %}}
 
 {{% nextSection %}}

docs/content/docs/jmc/method_profiling.md

@@ -17,7 +17,7 @@ This page is a little bit difficult to use in JMC7, planned improvements for the
 
 ![](/jmc/method_profile_page.png)
 
-By default, this view groups threads by method, but you can also include the line number for each method. This can be accomplishbed by selecting the __View Menu__ option and  going to __Distinguish Frames By__ and selecting __Line Number__.
+By default, this view groups threads by method, but you can also include the line number for each method. This can be accomplished by selecting the __View Menu__ option and  going to __Distinguish Frames By__ and selecting __Line Number__.
 
 ![](/jmc/method_profile_distinguish_line_numbers.png)
 
@@ -52,7 +52,7 @@ We can then use this information to correlate what is happening in our code:
 ## <i class="fas fa-compass"></i> Explore
 
 * Walk around to look at other areas where you are spending time in your code. 
-  * In many cases you find that there are very expensive areas of code that you cannot change (as you may not own it), but you can dictate whether or not it should be executed (or executed as frequently.
+  * In many cases you find that there are very expensive areas of code that you cannot change (as you may not own it), but you can dictate whether or not it should be executed (or executed as frequently).
 
 ### <i class="fas fa-question"></i> Follow Ups
 

docs/content/docs/jmc/open_jdk_9+.jfc

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<configuration version="2.0" label="Java Perfomance Workshop JDK 9+ Profile" description="Low overhead configuration for profiling, typically around 2 % overhead." provider="Oracle">
+<configuration version="2.0" label="Java Performance Workshop JDK 9+ Profile" description="Low overhead configuration for profiling, typically around 2 % overhead." provider="Oracle">
 
   <event name="jdk.ThreadAllocationStatistics">
     <setting name="enabled">true</setting>

docs/content/docs/jmc/threads.md

@@ -5,7 +5,7 @@ description: >
     Find the computation and latency events in your application.
 ---
 
-The __Threads__ page provides a snaphost of all threads in our application, and we can use it to acquire information about computation and latency events.
+The __Threads__ page provides a snapshot of all threads in our application, and we can use it to acquire information about computation and latency events.
 
 ![](/jmc/threads_page.png)
 
@@ -33,7 +33,7 @@ Once you're done with the filtered view, right click on the __Thread__ page and
 
 ### By Thread
 
-We can select an invididual thread from the __Thread Table__ to further filter the data just for that thread. From this filtered view, we can inspect what the commonly executed methods are for a particular thread. 
+We can select an individual thread from the __Thread Table__ to further filter the data just for that thread. From this filtered view, we can inspect what the commonly executed methods are for a particular thread. 
 
 ![](/jmc/thread_selected.png)
 

docs/content/docs/prereqs/_index.md

@@ -2,7 +2,7 @@
 title: "Prerequisites"
 weight: 5
 description: >
-    Instructions for acquiring the sofware needed for the workshop.
+    Instructions for acquiring the software needed for the workshop.
 hide_readingtime: true
 ---