Fix table formatting

Author: ecfan

articles/logic-apps/logic-apps-securing-a-logic-app.md

@@ -455,7 +455,6 @@ This example template that has multiple secured parameter definitions that use t
 | `TemplateUsernameParam` | A template parameter that accepts a username that is then passed to the workflow definition's `basicAuthUserNameParam` parameter |
 | `basicAuthPasswordParam` | A workflow definition parameter that accepts the password for basic authentication in an HTTP action |
 | `basicAuthUserNameParam` | A workflow definition parameter that accepts the username for basic authentication in an HTTP action |
-|||
 
 ```json
 {
@@ -645,7 +644,6 @@ Each URL contains the `sp`, `sv`, and `sig` query parameter as described in this
 | `sp` | Specifies permissions for the allowed HTTP methods to use. |
 | `sv` | Specifies the SAS version to use for generating the signature. |
 | `sig` | Specifies the signature to use for authenticating access to the trigger. This signature is generated by using the SHA256 algorithm with a secret access key on all the URL paths and properties. This key is kept encrypted, stored with the logic app, and is never exposed or published. Your logic app authorizes only those triggers that contain a valid signature created with the secret key. |
-|||
 
 Inbound calls to a request endpoint can use only one authorization scheme, either SAS or [OAuth with Microsoft Entra ID](#enable-oauth). Although using one scheme doesn't disable the other scheme, using both schemes at the same time causes an error because the service doesn't know which scheme to choose.