cosmetics

Author: slavipande

tutorials/add-authorization/add-authorization.md

@@ -97,7 +97,7 @@ CAP offers a possibility to add local users for testing as part of the `cds` con
 
     The code creates the `cds.requires` section that didn't exist so far in the **package.json** file. Also, the code defines which configuration to use when running with the `[development]` profile. You define some general parameters for the authentication behavior. Notice that the users object is empty, in the next step, you will define some test users.
 
-3. In the **package.json** file, replace the empty `users` object with the `user` object from following code:
+3. In the **package.json** file, replace the empty `users` object with the `users` object from following code:
 
     ```json
     "cds": {

tutorials/add-fiori-elements-uis/add-fiori-elements-uis.md

@@ -73,7 +73,7 @@ To learn more about each of these points, see [Why Use SAP Fiori Elements?](http
 
     - In the **Main entity** dropdown menu, select **Incidents**.
 
-    - Leave the **Navigation entity** value as **none**, and then select **Yes** to add table columns automatically.
+    - Leave the **Navigation entity** value as **None**, and then select **Yes** to add table columns automatically.
 
     - In the **Table Type** dropdown menu, select **Responsive**.
 
@@ -91,7 +91,7 @@ To learn more about each of these points, see [Why Use SAP Fiori Elements?](http
 
     - Leave the default values for all the other settings and choose **Finish**.
 
-        <!-- border; size:540px --> ![Project names](./vscrfeapp.png)
+        <!-- border; size:540px --> ![Project names](./vscrfeapp.jpg)
 
     The application is now generated and in a few seconds you can see the application's **incidents** folder in the **app** folder of your **incident-management** project. It contains a **webapp** folder with a **Component.js** file that is typical for an SAPUI5 application. However, the source code of this application is minimal. It inherits its logic from the **sap/fe/core/AppComponent** class. This class is managed centrally by SAP Fiori elements and provides all the services that are required (routing, edit flow) so that the building blocks and the templates work properly.