Remove a debug log and tweak some doc wording.

app/info.cpp

@@ -71,15 +71,13 @@ void Info::run()
         std::cout << "\tResolved." << std::endl;
     }
 
-    std::cout << "Parsing" << std::endl;
     const std::string output = config::getOutput(m_json);
     const std::string tmp = config::getTmp(m_json);
     const bool deep = config::getDeep(m_json);
     const unsigned threads = config::getThreads(m_json);
     const json pipeline = config::getPipeline(m_json);
     const auto reprojection = config::getReprojection(m_json);
     const std::string summaryFilename = m_json.value("summary", "");
-    std::cout << "Parsed" << std::endl;
 
     if (inputs.empty()) throw std::runtime_error("No files found!");
 

doc/source/download.rst

@@ -47,14 +47,3 @@ Conda
 The fastest way to get going with Entwine is to use the Conda build.  See the
 :ref:`Quickstart` for more information.  The Conda build will always contain
 the most recent released version of Entwine.
-
-Docker
-................................................................................
-
-Or use the Docker image for the latest code:
-
-::
-
-    docker pull connormanning/entwine
-    docker run -it connormanning/entwine --help
-

readme.md

@@ -46,4 +46,6 @@ Going further
 
 For detailed information about how to configure your builds, check out the [configuration documentation](https://entwine.io/configuration.html).  Here, you can find information about reprojecting your data, using configuration files and templates, enabling S3 capabilities, and all sorts of other settings.
 
-To learn about the Entwine Point Tile file format produced by Entwine, see the [file format documentation](https://entwine.io/entwine-point-tile.html).
+To learn about the Entwine Point Tile (EPT) file format produced by Entwine, see the [file format documentation](https://entwine.io/entwine-point-tile.html).
+
+For an alternative method of generating EPT which can also generate [COPC](https://copc.io) data, see the [Untwine](https://github.com/hobuinc/untwine) project.