From 4fce83663cfbfc6ee7be35ca8ef5ae5c96ec56a7 Mon Sep 17 00:00:00 2001 From: Trevor Bramwell Date: Thu, 19 Oct 2017 10:54:11 -0700 Subject: [PATCH] Fix table formatting in api_mapping Change-Id: Ia76924629a450e51fc2a2bdbf7821a3c5f7a053e Signed-off-by: Trevor Bramwell --- docs/development/manuals/api_mapping.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/manuals/api_mapping.rst b/docs/development/manuals/api_mapping.rst index 6a1bfb7..c92e09b 100644 --- a/docs/development/manuals/api_mapping.rst +++ b/docs/development/manuals/api_mapping.rst @@ -277,7 +277,7 @@ II.a) REQUEST | Filter | | meta-data information or status information | on a filter. In Blazar you can either list all | | | | expressing the type of information to be | leases registered in Blazar (GET /v1/leases) or | | | | retrieved. It can also be used to specify one | show information about a specific lease | -| | | or more reservations to be queried by | (GET /v1/leases/{lease-id}). | +| | | or more reservations to be queried by | (GET /v1/leases/{lease-id}). | | | | providing their identifiers. | | +----------------------------------+--------------------------------------+------------------------------------------------+-------------------------------------------------+ -- 2.16.6