Correct quotes in JSON and ABAP samples

docs/30-development/accessing-business-service-ui-0f1f92e.md

@@ -9,22 +9,23 @@ Business Service UI's must be stored in HTML5 Application Repository and defined
 The following is an example `manifest.json` file of a Business Service:
 
 > ### Sample Code:  
-> ```
+> ```JSON
 > {
->   “sap.app”: {
->     “id”:“com.sap.appbasic.country.list”,
->     “applicationVersion: {
->     “version”: “1.0.0”
+>   "sap.app": {
+>     "id":"com.sap.appbasic.country.list",
+>     "applicationVersion": {
+>       "version": "1.0.0"
+>     }
 >   },
 >   "dataSources": {
 >     "mainService":{
 >       "uri": "odata/v2/countryservice",
 >       "type": "OData"
 >     }
 >   },
->   “sap.cloud”: {
+>   "sap.cloud": {
 >     "public": true,
->     “service”: “com.sap.appbasic.country“
+>     "service": "com.sap.appbasic.country"
 >   }
 > }
 > ```
@@ -46,4 +47,3 @@ In this example, `comsapappbasiccountry` is the business service prefix which ma
 [Integration with Business Services](integration-with-business-services-f6337cd.md "Application router supports integration with Business Services, which are a flavor of reuse-services.")
 
 [Accessing Business Service Data](accessing-business-service-data-783809d.md "This section describes how the application router accesses the Business Service data.")
-

docs/30-development/actions-and-functions-cea94cf.md

@@ -85,10 +85,9 @@ POST /sap/opu/odata4/iwbep/tea/default/iwbep/tea_busi/0001/EMPLOYEES('2')/SAP__s
 
 Request body:
 
-```
-
+```JSON
 { 
-"TeamID" : "TEAM_02" 
+  "TeamID" : "TEAM_02" 
 }
 ```
 
@@ -130,5 +129,3 @@ For examples and steps for Import and Bound operations, see:
 -   System query options are **not** supported for Version 4 functions.
 
 -   If the return type of a Version 2 function is an entity type and this entity type is used by more than one entity set, the Version 2 request context only contains the \(EDM\) name of the first entity set with the underlying entity type. A precise mapping is currently not possible. For remote consumption, this can be handled in the proxy model by setting the correct entity set via method .`/iwbep/if_v4_med_func_imp->set_entity_set_name`
-
-

docs/30-development/add-authentication-and-functional-authorization-checks-to-your-application-0a69484.md

@@ -35,7 +35,7 @@ You declare your application security descriptor with JSON syntax and store it i
     Scopes represent the API endpoints - or functions - for which access should be restricted. They’re required if you want to define the functions a user is authorized to process. A scope has an arbitrary name and must be prefixed with the runtime application name to distinguish the user scopes between tenants \(subaccounts\) which have subscribed to the application and equally named scopes between different applications. The `$XSAPPNAME` dummy value is a wildcard for the application runtime name and is used to prefix the arbitrary scope names. The XSUAA service substitutes the `$XSAPPNAME` dummy value with the application runtime name for each of the subscribed tenants \(see also step 1\).
 
     > ### Sample Code:  
-    > ```
+    > ```JSON
     > {
     >   ... 
     >   "scopes"    : [
@@ -60,7 +60,7 @@ You declare your application security descriptor with JSON syntax and store it i
     Attributes provide instance-based, fine-granular authorization checks. See [Setting Up Instance-Based Authorizations](setting-up-instance-based-authorizations-519965c.md).
 
     > ### Sample Code:  
-    > ```
+    > ```JSON
     > {
     >   ...
     >   "attributes" : [
@@ -82,7 +82,7 @@ You declare your application security descriptor with JSON syntax and store it i
     Role templates combine scopes with attributes and serve as templates from which roles are created later by the administrator.
 
     > ### Sample Code:  
-    > ```
+    > ```JSON
     > {
     >   ...
     >   "role-templates" : [
@@ -112,7 +112,7 @@ You declare your application security descriptor with JSON syntax and store it i
 6.  Check the scopes in the application.
 
     > ### Sample Code:  
-    > ```
+    > ```JavaScript
     > app.get('/books', checkReadScope, getBooks);
     > 
     > // Scope check
@@ -156,7 +156,7 @@ You declare your application security descriptor with JSON syntax and store it i
 You’ve declared and deployed your application security descriptor \(`xs-security.json`\) with scopes \(functional authorizations\), attributes \(data authorizations\), and role templates \(to combine scopes with attributes\). The `xsappname` element is mandatory. The `scopes`, `attributes`, and `role-templates` elements are optional. You've also bound your service instance to your application, and then deployed it.
 
 > ### Sample Code:  
-> ```
+> ```JSON
 > {
 >   "xsappname" : "hello-world", 
 >   "scopes"    : [
@@ -213,4 +213,3 @@ To implement web access using a browser or a browser-based user interface, you c
 [Limits for Technical Artifacts of the SAP Authorization and Trust Management Service](../60-security/limits-for-technical-artifacts-of-the-sap-authorization-and-trust-management-service-6d3ef52.md "To improve the resiliency of the SAP Authorization and Trust Management service, we have introduced limitations on technical artifacts of the service.")
 
 [Application Security Descriptor Configuration Syntax](application-security-descriptor-configuration-syntax-517895a.md "The syntax required to set the properties and values defined in the xs-security.json application security descriptor file.")
-

docs/30-development/add-custom-soap-header-elements-3dadfa9.md

@@ -96,7 +96,7 @@ The following example shows how to adjust the SOAP request header followed by th
 
 The resulting SOAP request looks like this:
 
-```
+```XML
 <?xml version="1.0" encoding="UTF-8"?>
 <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <env:Header>
@@ -118,4 +118,3 @@ The resulting SOAP request looks like this:
 
 
 [Set Up SOAP Communication](set-up-soap-communication-8b6723b.md "To set up SOAP communication, use the corresponding communication management apps.")
-

docs/30-development/application-router-configuration-c19f165.md

@@ -96,7 +96,7 @@ You can configure the application router to send additional HTTP headers, for ex
 > ### Sample Code:  
 > `local-http.headers.json`
 > 
-> ```
+> ```JSON
 > [
 >   {
 >     "X-Frame-Options": "ALLOW-FROM http://localhost"
@@ -194,7 +194,7 @@ The application-router process should run with at least 256MB memory. The amount
 You can use the start-up parameter `max-old-space-size` to restrict the amount of memory used by the JavaScript heap. The default value for `max-old-space-size` is less than 2GB. To enable the application to use all available resources, the value of `max-old-space-size` should be set to a number equal to the memory limit for the whole application. For example, if the application memory is limited to 2GB, set the heap limit as follows, in the application's `package.json` file:
 
 > ### Sample Code:  
-> ```
+> ```JSON
 > "scripts": {
 >   "start": "node --max-old-space-size=2048 node_modules/@sap/approuter/approuter.js"
 > }
@@ -203,7 +203,7 @@ You can use the start-up parameter `max-old-space-size` to restrict the amount o
 If the application router is running in an environment with limited memory, set the heap limit to about 75% of available memory. For example, if the application router memory is limited to 256MB, add the following command to your `package.json`:
 
 > ### Sample Code:  
-> ```
+> ```JSON
 > "scripts": {
 >   "start": "node --max-old-space-size=192 node_modules/@sap/approuter/approuter.js"
 > }
@@ -260,4 +260,3 @@ The `@sap/logging` package sets the header `x-request-id` in the application rou
 [Application Router](application-router-01c5f9b.md "The application router is the single point-of-entry for an application running in the Cloud Foundry environment on SAP BTP. The application router is used to serve static content, authenticate users, rewrite URLs, and forward or proxy requests to other micro services while propagating user information.")
 
 [Resource Files](resource-files-e179c0c.md "The routing configuration for an application is defined in one or more destinations.")
-

docs/30-development/create-pull-c4b8a97.md

@@ -203,7 +203,7 @@ Request body
 > Accept: application/json
 > 
 > {
-> 	“sc_name” : “/DMO/GIT_REPOSITORY”
+> 	"sc_name" : "/DMO/GIT_REPOSITORY"
 > }
 > 
 > ```
@@ -311,4 +311,3 @@ Could not read the pull job. Please check the parameters.
 > }
 > 
 > ```
-

docs/30-development/delete-data-from-the-database-c5758c7.md

@@ -366,27 +366,27 @@ Typical flow of the archiving delete process:
 > DATA:   ls_index TYPE my_index_table.
 >              
 > 
->  “ get newest undeleted file
+>  " get newest undeleted file
 >       DATA(lt_files) = cl_arch_delete_api=>get_files_to_delete( iv_archiving_object =     lc_object ).
 >               SORT lt_files BY creation_date DESCENDING creation_time DESCENDING.
 >               READ TABLE lt_files ASSIGNING FIELD-SYMBOL(<ls_file>) INDEX 1.	
 > 
 >             DATA(lo_delete) = cl_arch_delete_api=>get_instance
 > ( iv_archiving_object = lc_object                                                                                 iv_archive_key = lv_arkey
 >                                                      iv_testmode = lv_test ).
->             “ read next data object from archive file into internal memory
+>             " read next data object from archive file into internal memory
 >             DO.
 >               lo_delete->get_next_data_object( IMPORTING ev_end_of_file = DATA(lv_end_of_file)
 >                                                          ev_archive_key = DATA(lv_archive_key)
 >                                                          ev_object_offset = DATA(lv_offset) ).
 >               IF lv_end_of_file = abap_true.
 >                 EXIT.
 >               ENDIF.
->               “ optional: Create customer owned index for single document access during read
->               “ read archived data for table MY_HEADER_TABLE
+>               " optional: Create customer owned index for single document access during read
+>               " read archived data for table MY_HEADER_TABLE
 >               lo_delete->get_data_records( EXPORTING iv_record_structure = ‘MY_HEADER_TABLE’
 >                                            IMPORTING et_data_records = lt_data ).
->               “ map flight data to your index table MY_INDEX_TABLE
+>               " map flight data to your index table MY_INDEX_TABLE
 >               IF lv_test <> abap_true.
 >                 LOOP AT lt_data ASSIGNING FIELD-SYMBOL(<ls_data>).
 >                   MOVE-CORRESPONDING <ls_data> TO ls_index.
@@ -395,7 +395,7 @@ Typical flow of the archiving delete process:
 >                   INSERT my_index_table FROM @ls_Index.
 >                 ENDLOOP.
 >               ENDIF.
->               “ delete the data from the data base
+>               " delete the data from the data base
 >               lo_delete->delete_data_for_object( ).
 >             ENDDO.
 >             COMMIT WORK.  
@@ -425,4 +425,3 @@ Example of a customer-owned index table for archived flights:
 > archive_offset : sarch_offset;
 > 
 > ```
-

docs/30-development/environment-variables-ba52705.md

@@ -1053,12 +1053,12 @@ Yes
 </td>
 <td valign="top">
 
-A comma-separated list of objects each of which contains a host name, port and protocol that are allowed by the server, for example: `[{“host”: "www.acme.com"}]` or `[{“host”: “.acme.com”}]`.
+A comma-separated list of objects each of which contains a host name, port and protocol that are allowed by the server, for example: `[{"host": "www.acme.com"}]` or `[{"host": ".acme.com"}]`.
 
 > ### Note:  
-> Matching is case-sensitive. In addition, if no port or protocol is specified, the default is `“*”`.
+> Matching is case-sensitive. In addition, if no port or protocol is specified, the default is `"*"`.
 
-The default configuration is: `[{“host”: "*"}]`, which means that the server allows **any** origin to access the resource.
+The default configuration is: `[{"host": "*"}]`, which means that the server allows **any** origin to access the resource.
 
 </td>
 </tr>
@@ -1262,4 +1262,3 @@ Here is a sample content for the `CF_NODEJS_LOGGING_LEVEL` environment variable:
 [Application Router](application-router-01c5f9b.md "The application router is the single point-of-entry for an application running in the Cloud Foundry environment on SAP BTP. The application router is used to serve static content, authenticate users, rewrite URLs, and forward or proxy requests to other micro services while propagating user information.")
 
 [Routing Configuration File](routing-configuration-file-c103fb4.md "The routing configuration defined in the xs-app.json file contains the properties used by the application router.")
-

docs/30-development/parameters-and-properties-490c8f7.md

@@ -786,7 +786,7 @@ To enable resource properties to resolve values from a property in another resou
 > ### Code Syntax:  
 > Cross-References between Properties in the MTA Deployment Descriptor
 > 
-> ```
+> ```YAML
 > 
 > modules: 
 >   - name: java 
@@ -984,4 +984,3 @@ The following example shows the dependency declaration in the deployment descrip
 > ```
 
 For more information about cross-MTA configurations see [Cross-MTA Dependencies](cross-mta-dependencies-b8e1953.md).
-

docs/30-development/select-data-and-write-it-to-archive-files-f24d613.md

@@ -243,19 +243,19 @@ Typical flow of the archiving write process:
 > ### Sample Code:  
 > ```abap
 > CONSTANTS: lc_object TYPE sarch_object VALUE ‘MY_OBJECT’. 
-> “ Replace with the name of your ADT archiving object
-> “ select flight data (leading table) from the database (replace table names with your names of your own tables)
+> " Replace with the name of your ADT archiving object
+> " select flight data (leading table) from the database (replace table names with your names of your own tables)
 >         SELECT * FROM my_header_table
 >                  WHERE carrid     IN @lt_range_carrid
 >                    AND connid     IN @lt_range_connid
 >                    AND fldate     IN @lt_range_fldate
 >           INTO TABLE @DATA(lt_flights).
->         “ open a new archiving session to archive data
+>         " open a new archiving session to archive data
 >         TRY.
 >             DATA(lo_write) = cl_arch_write_api=>get_instance( iv_archiving_object = lc_object 								  iv_testmode = lv_test ).
 > 
 >             LOOP AT lt_flights ASSIGNING FIELD-SYMBOL(<ls_flight>).
->  “ select data of dependent tables (replace table names with your names of your own tables)
+>  " select data of dependent tables (replace table names with your names of your own tables)
 >               INSERT <ls_flight> INTO lt_flights.
 >               SELECT * FROM my_item_table1
 >                  WHERE carrid     = @<ls_flight>-carrid
@@ -273,28 +273,27 @@ Typical flow of the archiving write process:
 >                    AND fldate     = @<ls_flight>-fldate
 >                INTO TABLE @DATA(lt_invoices).
 > 
->               “ open new ADK data object
+>               " open new ADK data object
 >               lo_write->open_data_object( ).
 > 
->               “ write data of header table
+>               " write data of header table
 >               lo_write->put_data_records( iv_table_name = ‘<MY_HEADER_TALBE>’ it_records = lt_sflight_arch ).
 >               CLEAR lt_sflight_arch.
 > 
->               “ write data of depending tables
->               lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE1>’ it_records = lt_bookings ). “ bookings
+>               " write data of depending tables
+>               lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE1>’ it_records = lt_bookings ). " bookings
 >               CLEAR lt_sflight_arch.
->               Lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE2>’ it_records = lt_tickets ). “ tickets
+>               Lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE2>’ it_records = lt_tickets ). " tickets
 >               CLEAR lt_sflight_arch.
->               Lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE3>’ it_records = lt_invoices ). “ invoices
+>               Lo_write->put_data_records( iv_table_name = ‘<MY_ITEM_TABLE3>’ it_records = lt_invoices ). " invoices
 >               CLEAR lt_sflight_arch.
 > 
->               “ write data object into the archive file
+>               " write data object into the archive file
 >               lo_write->close_data_object( ).
 > 
 >             ENDLOOP.
 > 
->             “ finalize and end writing
+>             " finalize and end writing
 >             lo_write->finalize( ).
 > 
 > ```
-

docs/50-administration-and-ops/managing-resource-providers-e2c250d.md

@@ -110,12 +110,12 @@ To consume the resources provisioned by your provider account, you need to first
     > ### Sample Code:  
     > Sample JSON for configuring Amazon Web Services \(AWS\) as a resource provider:
     > 
-    > ```
+    > ```JSON
     > {
-    > “access_key_id”: “AWSACCESSKEY”,
-    > “secret_access_key”: “SECRETKEY”,
-    > “vpc_id”: “vpc-test”,
-    > “region”: “eu-central-1”
+    >   "access_key_id": "AWSACCESSKEY",
+    >   "secret_access_key": "SECRETKEY",
+    >   "vpc_id": "vpc-test",
+    >   "region": "eu-central-1"
     > }
     > 
     > ```
@@ -243,4 +243,3 @@ Follow these steps to manage the resource providers that you have already config
 
 
 [Configure Entitlements and Quotas for Subaccounts](configure-entitlements-and-quotas-for-subaccounts-5ba357b.md "Distribute the entitlements that are available in your global account by adding service plans and their allowed quotas to your subaccounts using SAP BTP cockpit.")
-