fix no-break spaces

Author: cpholguera

Document/0x04c-Tampering-and-Reverse-Engineering.md

@@ -190,7 +190,7 @@ In a real world situation, the functions are much more complex than the above ex
 - Complex equations generated by symbolic execution may not be solvable by SMT solvers because of their limitations.
 - Program is using system calls, library calls or network events which cannot be handled by symbolic execution.
 
-To overcome these challenges, typically, symbolic execution is combined with other techniques such as _dynamic execution_ (also called _concrete execution_) to mitigate the path explosion problem specific to classical symbolic execution. This combination of concrete (actual) and symbolic execution is referred to as _concolic execution_ (the name concolic stems from **conc**rete and symb**olic**), sometimes also called as _dynamic symbolic execution_.
+To overcome these challenges, typically, symbolic execution is combined with other techniques such as _dynamic execution_ (also called _concrete execution_) to mitigate the path explosion problem specific to classical symbolic execution. This combination of concrete (actual) and symbolic execution is referred to as _concolic execution_ (the name concolic stems from **conc**rete and symb**olic**), sometimes also called as _dynamic symbolic execution_.
 
 To visualize this, in the above example, we can obtain the value of the external variable by performing further reverse engineering or by dynamically executing the program and feeding this information into our symbolic execution analysis. This extra information will reduce the complexity of our equations and may produce more accurate analysis results. Together with improved SMT solvers and current hardware speeds, concolic execution allows to explore paths in medium-size software modules (i.e., on the order of 10 KLOC).
 

Document/0x05j-Testing-Resiliency-Against-Reverse-Engineering.md

@@ -71,28 +71,28 @@ The default daily limit for Google Play Services Integrity Verification API requ
 
 ```json
 {
-   "requestDetails": {
-     "requestPackageName": "com.example.your.package",
-     "timestampMillis": "1666025823025",
-     "nonce": "kx7QEkGebwQfBalJ4...Xwjhak7o3uHDDQTTqI"
-   },
-   "appIntegrity": {
-     "appRecognitionVerdict": "UNRECOGNIZED_VERSION",
-     "packageName": "com.example.your.package",
-     "certificateSha256Digest": [
-       "vNsB0...ww1U"
-     ],
-     "versionCode": "1"
-   },
-   "deviceIntegrity": {
-     "deviceRecognitionVerdict": [
-       "MEETS_DEVICE_INTEGRITY"
-     ]
-   },
-   "accountDetails": {
-     "appLicensingVerdict": "UNEVALUATED"
-   }
- }
+   "requestDetails": {
+     "requestPackageName": "com.example.your.package",
+     "timestampMillis": "1666025823025",
+     "nonce": "kx7QEkGebwQfBalJ4...Xwjhak7o3uHDDQTTqI"
+   },
+   "appIntegrity": {
+     "appRecognitionVerdict": "UNRECOGNIZED_VERSION",
+     "packageName": "com.example.your.package",
+     "certificateSha256Digest": [
+       "vNsB0...ww1U"
+     ],
+     "versionCode": "1"
+   },
+   "deviceIntegrity": {
+     "deviceRecognitionVerdict": [
+       "MEETS_DEVICE_INTEGRITY"
+     ]
+   },
+   "accountDetails": {
+     "appLicensingVerdict": "UNEVALUATED"
+   }
+ }
 ```
 
 #### Programmatic Detection