Build: Rename install export dir to interface
To make it more clear that it contains the ns interface sources, headers
and static libraries, and to allow more clear installation of other
components.
Change-Id: Id02bd472270b55245ea804437bd21d1dca24b7d8
Signed-off-by: Raef Coles <raef.coles@arm.com>
diff --git a/docs/getting_started/tfm_integration_guide.rst b/docs/getting_started/tfm_integration_guide.rst
index e883750..fc729a5 100644
--- a/docs/getting_started/tfm_integration_guide.rst
+++ b/docs/getting_started/tfm_integration_guide.rst
@@ -117,9 +117,9 @@
Interface with TF-M
===================
The files needed for the interface with TF-M are exported at the
-``<install_dir>/export/tfm`` path. The NS side is only allowed to call
+``<install_dir>/interface`` path. The NS side is only allowed to call
TF-M secure functions (veneers) from the NS Thread mode. For this reason, the
-API is a collection of functions in the ``<install_dir>/export/tfm/inc``
+API is a collection of functions in the ``<install_dir>/interface/include``
directory. For example, the interface for the Protected Storage (PS) service
is described in the file ``psa_ps_api.h`` as a collection of functions that
call service veneer functions. This API is a wrapper for the secure veneers,