anchor.diff:  
   ---
   
  -For this to work you need to make sure your Mongo and SOLR server is running. You don't need a Neo4J server as OLS uses an embedded Neo4J database. If you already have a tomcat server running with OLS deployed and it is using the same index files as SOLR and Neo4J, it is advisable to shutdown the tomcat before running this script.
  +For this to work you need to make sure your Mongo and SOLR servers are running. You don't need a Neo4J server as OLS uses an embedded Neo4J database. If you already have a tomcat server running with OLS deployed and it is using the same index files as SOLR and Neo4J, it is advised to shutdown the tomcat before running this script.
   
   To invoke the indexer process you can run the file ols-loading-app.jar (`java -jar ols-loading-app.jar`) in the folder OLS/ols-apps/ols-loading-app/target.
   
  
positive.code: 
  At this point the config should be loaded into your mongo db database called ols and a document collection called olsadmin.
  
  If you need to update any config or reload the config simply re-run the config-loader.jar as required.
  
  === Building the Neo4J and SOLR indexes
  OLS provide a single application for indexing ontologies. When run this program does a few things:
  
  ---
  
  
negative.code: #Mongo DB properties same as above
  ----------------
  
  By default OLS will use ~/.ols as the working directory for OLS where files will be downloaded and Neo4J indexes will be created. You can override this by setting the $OLS_HOME environment variable to a custom directory. You can also override this by passing the ``-Dols.home=` argument to any of the scripts.
  
  Providing this script has run successfully, you can rerun this script to update the OLS indexes. Each time you run it it will fetch the latest ontologies and only index the ones that have changed. Remember to shut down the tomcat before running this app.
  
  
  == Deploying the app on local server
  