Change most occurences of PROJ.4 to PROJ [skip ci]

5 files changed, 19 insertions, 19 deletions

diff --git a/docs/source/development/bindings.rst b/docs/source/development/bindings.rst
index 80babcb2..3fac1869 100644
--- a/docs/source/development/bindings.rst
+++ b/docs/source/development/bindings.rst
@@ -4,40 +4,40 @@
 Language bindings
 ********************************************************************************
 
-PROJ.4 bindings are available for a number of different development platforms.
+PROJ bindings are available for a number of different development platforms.
 
 Python
 ======
 `pyproj <http://pypi.python.org/pypi/pyproj>`_:
-Python interface (wrapper for PROJ.4)
+Python interface (wrapper for PROJ)
 
 
 Ruby
 =======
 
 `proj4rb <http://proj4rb.rubyforge.org>`_:
-Bindings for PROJ.4 in ruby
+Bindings for PROJ in ruby
 
 TCL
 ========
 `proj4tcl <http://wiki.tcl.tk/41270>`_:
-Bindings for PROJ.4 in tcl (critcl source)
+Bindings for PROJ in tcl (critcl source)
 
 MySQL
 =====
 
 `fProj4 <http://sourceforge.net/projects/mysqlscientific/files/fPROJ4/>`_:
-Bindings for PROJ.4 in MySQL
+Bindings for PROJ in MySQL
 
 
 Excel
 ========
 
 `proj.xll <https://github.com/jbuonagurio/proj.xll>`_:
-Excel add-in for PROJ.4 map projections
+Excel add-in for PROJ map projections
 
 Visual Basic
 ==================
 
-`PROJ.4 VB Wrappers <http://ftp.dfg.ca.gov/Public/BDB/Tools/proj4/proj_api.zip>`_:
+`PROJ VB Wrappers <http://ftp.dfg.ca.gov/Public/BDB/Tools/proj4/proj_api.zip>`_:
 By Eric G. Miller.
diff --git a/docs/source/development/cmake.rst b/docs/source/development/cmake.rst
index 1429ae88..5a8ce624 100644
--- a/docs/source/development/cmake.rst
+++ b/docs/source/development/cmake.rst
@@ -1,10 +1,10 @@
 .. _cmake:
 
 ********************************************************************************
-Using Proj.4 in CMake projects
+Using PROJ in CMake projects
 ********************************************************************************
 
-The recommended way to use the Proj.4 library in a CMake project is to
+The recommended way to use the PROJ library in a CMake project is to
 link to the imported library target ``${PROJ4_LIBRARIES}`` provided by
 the CMake configuration which comes with the library. Typical usage is:
 
diff --git a/docs/source/development/index.rst b/docs/source/development/index.rst
index 743224a6..3f8a7bf6 100644
--- a/docs/source/development/index.rst
+++ b/docs/source/development/index.rst
@@ -5,7 +5,7 @@ Development
 ================================================================================
 
 These pages are primarily focused towards developers either contributing to the
-PROJ.4 project or using the library in their own software.
+PROJ project or using the library in their own software.
 
 
 .. toctree::
diff --git a/docs/source/development/quickstart.rst b/docs/source/development/quickstart.rst
index 7137d85a..960cddbf 100644
--- a/docs/source/development/quickstart.rst
+++ b/docs/source/development/quickstart.rst
@@ -4,15 +4,15 @@
 Quick start
 ================================================================================
 
-This is a short introduction to the PROJ.4 API. In the following section we
+This is a short introduction to the PROJ API. In the following section we
 create a simple program that transforms a geodetic coordinate to UTM and back
 again. The program is explained a few lines at a time. The complete program can
 be seen at the end of the section.
 
 See the following sections for more in-depth descriptions of different parts of
-the PROJ.4 API or consult the :doc:`API reference <reference/index>` for specifics.
+the PROJ API or consult the :doc:`API reference <reference/index>` for specifics.
 
-Before the PROJ.4 API can be used it is necessary to include the ``proj.h`` header
+Before the PROJ API can be used it is necessary to include the ``proj.h`` header
 file. Here ``stdio.h`` is also included so we can print some text to the screen:
 
 .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c
@@ -54,10 +54,10 @@ details.
   :lines: 50-52
   :dedent: 4
 
-PROJ.4 uses it's own data structures for handling coordinates. Here we use a
+PROJ uses it's own data structures for handling coordinates. Here we use a
 ``PJ_COORD`` which is easily assigned with the function ``proj_coord``. Note
 that the input values are converted to radians with ``proj_torad``. This is
-necessary since PROJ.4 is using radians internally. See :doc:`transformations`
+necessary since PROJ is using radians internally. See :doc:`transformations`
 for further details.
 
 .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c
diff --git a/docs/source/development/threads.rst b/docs/source/development/threads.rst
index a557fa07..674f4bd1 100644
--- a/docs/source/development/threads.rst
+++ b/docs/source/development/threads.rst
@@ -4,7 +4,7 @@
 Threads
 ================================================================================
 
-This page is about efforts to make PROJ.4 thread safe.
+This page is about efforts to make PROJ thread safe.
 
 Key Thread Safety Issues
 --------------------------------------------------------------------------------
@@ -14,14 +14,14 @@ Key Thread Safety Issues
   introduction of the projCtx execution context.
 * the datum shift using grid files uses globally shared lists of loaded grid
   information. Access to this has been made safe in 4.7.0 with the introduction
-  of a proj.4 mutex used to protect access to these memory structures (see
+  of a PROJ mutex used to protect access to these memory structures (see
   pj_mutex.c).
 
 projCtx
 --------------------------------------------------------------------------------
 
 Primarily in order to avoid having pj_errno as a global variable, a "thread
-context" structure has been introduced into a variation of the PROJ.4 API for
+context" structure has been introduced into a variation of the PROJ API for
 the 4.8.0 release.  The pj_init() and pj_init_plus() functions now have context
 variations called pj_init_ctx() and pj_init_plus_ctx() which take a projections
 context.
@@ -68,7 +68,7 @@ src/multistresstest.c
 --------------------------------------------------------------------------------
 
 A small multi-threaded test program has been written (src/multistresstest.c)
-for testing multithreaded use of PROJ.4.  It performs a series of reprojections
+for testing multithreaded use of PROJ.  It performs a series of reprojections
 to setup a table expected results, and then it does them many times in several
 threads to confirm that the results are consistent.  At this time this program
 is not part of the builds but it can be built on linux like: