Updates

Author: apruneda

CHANGELOG.md

@@ -1,4 +1,4 @@
-# Splunk SDK for Java Changelog
+# Splunk Enterprise SDK for Java Changelog
 
 ## Version 1.6.5
 
@@ -130,7 +130,7 @@
 
 ### New features and APIs
 
-* The Splunk SDK for Java is fully compatible with Splunk Enterprise 6.0 as of this release.
+* The Splunk Enterprise SDK for Java is fully compatible with Splunk Enterprise 6.0 as of this release.
 
 ### Bug fixes
 
@@ -152,14 +152,14 @@
   OS X v10.9 Mavericks running Splunk 6.0.0. This issue is not present when running Splunk Enterprise on earlier
   versions of OS X. This will be fixed in a future release.
 
-* The modular input support in the Splunk SDK for Java is not compatible with Windows Server 2003 or Windows Server
+* The modular input support in the Splunk Enterprise SDK for Java is not compatible with Windows Server 2003 or Windows Server
   2003 R2.
 
 ## Version 1.2
 
 ### New features and APIs
 
-* Added support for building modular input scripts in Java using the Splunk SDK for Java.
+* Added support for building modular input scripts in Java using the Splunk Enterprise SDK for Java.
 
 ### Bug fixes
 
@@ -479,7 +479,7 @@ changes are not included):
 * Added a namespacing feature as optional arguments (`app`, `owner`, `sharing`)
   to the collection's `create` and `get` methods. For more information about
   namespaces, see
-  ["Overview of the Splunk SDK for Java"](http://dev.splunk.com/view/java-sdk/SP-CAAAECN)
+  ["Overview of the Splunk Enterprise SDK for Java"](http://dev.splunk.com/view/java-sdk/SP-CAAAECN)
   on the Developer Portal.
 
   The following example shows how to use the optional namespace to restrict
@@ -585,4 +585,4 @@ changes are not included):
 
 ## Version 0.1.0 (preview)
 
-Initial Splunk SDK for Java release.
+Initial Splunk Enterprise SDK for Java release.

CONTRIBUTING.md

@@ -2,42 +2,34 @@
 
 ## How to contribute
 
-If you would like to contribute to this project, see [Contributions to Splunk][indivcontrib] for more information.
+If you would like to contribute to this project, see [Contributions to Splunk][https://www.splunk.com/en_us/form/contributions.html] for more information.
 
-## Issues & Bug Reports
+## Issues and bug reports
 
-If you're seeing some unexpected behavior with this project, please create an [issue on GitHub][issues] with the following information:
+If you're seeing some unexpected behavior with this project, please create an [issue](https://github.com/splunk/splunk-sdk-java/issues) on GitHub with the following information:
 
 1. Version of this project you're using (ex: 1.4.0)
-1. Platform version (ex: Windows Server 2012)
-1. Framework version (ex: Java 8)
-1. Splunk version (ex: 6.2.2)
-1. Other relevant information (ex: local/remote environment, Splunk network configuration)
+2. Platform version (ex: Windows Server 2012)
+3. Framework version (ex: Java 8)
+4. Splunk version (ex: 6.2.2)
+5. Other relevant information (ex: local/remote environment, Splunk network configuration)
 
-Alternatively, if you have a Splunk question please ask on [Splunk Answers][answers]
+Alternatively, if you have a Splunk question please ask on [Splunk Answers](https://community.splunk.com/t5/Splunk-Development/ct-p/developer-tools).
 
 ## Pull requests
 
 We love to see pull requests!
 
 To create a pull request:
 
-1. Fill out the [Individual Contributor Agreement][indivcontrib].
-1. Fork [the repository][repo].
-1. Make changes to the **`develop`** branch, preferably with tests.
-1. Create a [pull request][pulls] against the **`develop`** branch.
+1. Fill out the [Individual Contributor Agreement][https://www.splunk.com/en_us/form/contributions.html].
+1. Fork the [repository][https://github.com/splunk/splunk-sdk-java].
+1. Make changes to the **develop** branch, preferably with tests.
+1. Create a [pull request][https://github.com/splunk/splunk-sdk-java/pulls] against the **develop** branch.
 
 ## Contact us
 
-You can [contact support][contact] if you have Splunk related questions.
+You can contact [Support][https://www.splunk.com/en_us/support-and-services.html] if you have questions.
 
-You can reach the Developer Platform team at _[email protected]_.
+You can reach the Splunk Developer Platform team at _[email protected]_.
 
-[contributions]:            http://dev.splunk.com/view/opensource/SP-CAAAEDM
-[indivcontrib]:             http://dev.splunk.com/goto/individualcontributions
-[companycontrib]:           http://dev.splunk.com/view/companycontributions/SP-CAAAEDR
-[answers]:                  http://answers.splunk.com/
-[repo]:                     https://github.com/splunk/splunk-sdk-java
-[issues]:                   https://github.com/splunk/splunk-sdk-java/issues
-[pulls]:                    https://github.com/splunk/splunk-sdk-java/pulls
-[contact]:                  https://www.splunk.com/en_us/support-and-services.html

README.md

@@ -247,7 +247,7 @@ Stay connected with other developers building on the Splunk platform.
 
 ### Contributions
 
-If you would like to contribute to the SDK, see [Contributions to Splunk](https://www.splunk.com/en_us/form/contributions.html).
+If you would like to contribute to the SDK, see [Contributing to Splunk](https://www.splunk.com/en_us/form/contributions.html). For additional guidelines, see [CONTRIBUTING](CONTRIBUTING.md). 
 
 ### Support
 

launchers/README.md

@@ -1,6 +1,6 @@
-# Modular input launchers for the Splunk SDK for Java
+# Modular input launchers for the Splunk Enterprise SDK for Java
 
-Splunk cannot launch Java programs as modular inputs directly. Instead, we need to provide a few small programs to launch a JVM and run a program. Since modular inputs written in Java need to work across all Splunk variants, including the universal forwarder, the launchers cannot rely on Python or anything else in the underlying system. Instead, we provide a set of C programs compiled for each of Linux, MacOS X, and Windows.
+Splunk Enterprise cannot launch Java programs as modular inputs directly. Instead, we need to provide a few small programs to launch a JVM and run a program. Since modular inputs written in Java need to work across all Splunk variants, including the universal forwarder, the launchers cannot rely on Python or anything else in the underlying system. Instead, we provide a set of C programs compiled for each of Linux, MacOS X, and Windows.
 
 The programs assume the following layout in an app: a jars/ directory containing a launchable jar containing the modular input, and a configuration file with a .ini suffix of the same base name that contains options for what JVM to launch and what options to pass to it. Then platform specific bin directories contain the launcher programs, named the base name of the target jar. For for a jar named myinput.jar, the layout would be