Provcide more flexiblity in using HIP_PATH to control installation.

Also improve docs for developers / contributing.


[ROCm/hip commit: f3ad047194]

projects/hip/README.md

@@ -6,7 +6,7 @@ Key features include:
 * HIP is very thin and has little or no performance impact over coding directly in CUDA or hcc "HC" mode.
 * HIP allows coding in a single-source C++ programming language including features such as templates, C++11 lambdas, classes, namespaces, and more.
 * HIP allows developers to use the "best" development environment and tools on each target platform.
-* The "hipify" script automatically converts source from CUDA to HIP.
+* The "hipify" tool automatically converts source from CUDA to HIP.
 * Developers can specialize for the platform (CUDA or hcc) to tune for performance or handle tricky cases 
 
 New projects can be developed directly in the portable HIP C++ language and can run on either NVIDIA or AMD platforms.  Additionally, HIP provides porting tools which make it easy to port existing CUDA codes to the HIP layer, with no loss of performance as compared to the original CUDA application.  HIP is not intended to be a drop-in replacement for CUDA, and developers should expect to do some manual coding and performance tuning work to complete the port.
@@ -19,7 +19,7 @@ cmake ..
 make
 sudo make install
 ```
-Make sure HIP_PATH is pointed to `/opt/hip` and PATH to `/opt/hip/bin`
+Make sure HIP_PATH is pointed to `/opt/hip` and PATH includes `$HIP_PATH/bin`
 
 ## More Info:
 - [HIP FAQ](docs/markdown/hip_faq.md)
@@ -27,6 +27,7 @@ Make sure HIP_PATH is pointed to `/opt/hip` and PATH to `/opt/hip/bin`
 - [HIP Runtime API (Doxygen)](http://gpuopen-professionalcompute-tools.github.io/HIP)
 - [HIP Porting Guide](docs/markdown/hip_porting_guide.md)
 - [HIP Terminology](docs/markdown/hip_terms.md) (including Rosetta Stone of GPU computing terms across CUDA/HIP/HC/AMP/OpenL)
+- [Developer/CONTRIBUTING Info](CONTRIBUTING.md)
 - [Release Notes](RELEASE.md)