update content for branding

Author: spboyer

powerapps-docs/guidance/fusion-dev-ebook/02-intro-sample-scenario.md

@@ -27,7 +27,7 @@ When a technician arrives at a customer's home and finds they don't have a part
 
 A solution is to create a app that allows the field technician to check inventory from the field and place an order immediately if that's necessary. The app will interface with a Web API running in Azure, that provides controlled access to the legacy inventory management system. The office inventory manager can connect to the same legacy system through a desktop app running on-premises. The desktop app enables the office inventory manager to see what parts are currently in stock, and when to place orders to replenish areas that are running low.
 
-![Field Inventory Management Power Apps app](media/image5.png)
+![Field Inventory Management app](media/image5.png)
 
 ## Field knowledgebase
 
@@ -41,7 +41,7 @@ It's impossible for one single technician to know everything about every model o
 
 A solution is to capture the information about furnaces and air conditioners, problems that have occurred, and how they were fixed, in a knowledge base. An app could allow a technician to record comments about a job and the repairs performed while still at the customer's premises. The same app could provide an interface that allows the technician to query the knowledge base about useful information that other technicians may have addressed on similar jobs. The knowledge base itself could be implemented as a database with Azure Cognitive Search providing the lookup facility, based on one or more key words.
 
-![Field Knowledgebase Power Apps app](media/image6.png)
+![Field Knowledgebase app](media/image6.png)
 
 ## Field scheduling and notes
 
@@ -61,7 +61,7 @@ There are several obvious drawbacks to the current scheduling strategy:
 
 VanArsdel could use an app that acts as a front end to the legacy system. It would enable the office receptionist staff to record appointments and cancellations, and add any additional notes to customer records. An app that's available to technicians can provide access to their appointments schedule in real time and see any changes. The same app should enable technicians to enter notes about a finished job and save this information back to the legacy system.
 
-![Field Scheduling Power Apps app](media/image7.png)
+![Field Scheduling app](media/image7.png)
 
 ## Fusion development team members
 

powerapps-docs/guidance/fusion-dev-ebook/03-building-low-code-prototype.md

@@ -17,7 +17,7 @@ ms.reviewer: kvivek
 > [!NOTE] 
 > [Chapter 2](02-intro-sample-scenario.md) referenced the mobile app used by the field technicians and engineers, and desktop Power Apps used by on-premises staff. The following chapters focus on the design, implementation, and rollout of the mobile apps built using Power Apps. The desktop apps are left as an exercise for the reader.
 
-Kiana is skeptical of low-code solutions and Power Apps, but she and Maria decide to build an app together to help the field technicians check inventory (and order parts if necessary), query the knowledge base, and check their next appointment while out of the office, on service calls. Kiana and Maria plan to use this experience to explore how to add controls and use formulas in a Power App.
+Kiana is skeptical of low-code solutions and Power Apps, but she and Maria decide to build an app together to help the field technicians check inventory (and order parts if necessary), query the knowledge base, and check their next appointment while out of the office, on service calls. Kiana and Maria plan to use this experience to explore how to add controls and use formulas in Power Apps.
 
 Although building an initial low-code prototype is primarily a typical citizen developer task, Kiana decides to pay attention to the process to ensure that she understands how the app is constructed. She needs this information to enable her to help Maria integrate the real-world data sources, Web APIs, and other services required into the app.
 
@@ -34,7 +34,7 @@ Maria is very familiar with the existing inventory management system and underst
 
 If you are a relational database designer, you'll notice that the Excel spreadsheet presents a denormalized view of the data. For example, in a relational database, **CategoryID** would most likely be a numeric identifier that references a separate table containing the details of the category, including the name.
 
-The URLs in the **Image** column are currently just placeholders. In the completed Power App, these URLs will be replaced with the addresses of real image files.
+The URLs in the **Image** column are currently just placeholders. In the completed app, these URLs will be replaced with the addresses of real image files.
 
 Follow these steps to create the app using Power Apps:
 
@@ -267,7 +267,7 @@ Maria decides to create a new screen based on the **List** template available in
 
 ## Item 3: Field scheduling and notes
 
-Maria works with Malik, the office receptionist, to design the interface for the field scheduling and appointments part of the Power App. Malik provides an Excel spreadsheet with some sample data that Maria can use to build the appointments screen. The spreadsheet contains a table with the following columns:
+Maria works with Malik, the office receptionist, to design the interface for the field scheduling and appointments part of the app. Malik provides an Excel spreadsheet with some sample data that Maria can use to build the appointments screen. The spreadsheet contains a table with the following columns:
 
 -   ID (the appointment ID)
 -   Customer ID (a unique identifier for the customer)
@@ -293,12 +293,12 @@ Maria stores this spreadsheet in her OneDrive account with the name **Appointmen
 
 Maria wants to build the appointments part of the app directly from the Excel spreadsheet. She decides to follow a similar approach to that of the Field Inventory Management functionality, except that this time the engineer will be allowed to create and edit appointments.
 
-Maria decides to build the appointments screens, initially as a separate Power App. This way, she can use Power Apps Studio to generate much of the app automatically. Power Apps Studio doesn't currently let you generate additional screens from a data connection in an existing app. When Maria has created and tested the screens, she will copy them to the Field Inventory and Knowledgebase app.
+Maria decides to build the appointments screens, initially as a separate app. This way, she can use Power Apps Studio to generate much of the app automatically. Power Apps Studio doesn't currently let you generate additional screens from a data connection in an existing app. When Maria has created and tested the screens, she will copy them to the Field Inventory and Knowledgebase app.
 
 > [!NOTE] 
 > An alternative approach is to add the **Appointments** table in the Excel spreadsheet as a second data source to the existing app and then hand-craft the screens for appointments. Maria opted to generate the new screens from the spreadsheet and copy the screens; she is currently more familiar with the concepts of *copy and paste* than building screens manually, although she will gradually learn how to create screens from scratch as the process of building this app progresses.
 
-You can follow these steps to create the Appointments Power App:
+You can follow these steps to create the Appointments app:
 
 1.  In Power Apps Studio, select the **File** menu in the toolbar.
 
@@ -468,7 +468,7 @@ Maria has built two apps, but she wants to combine them into a single app. To do
 
 1.  Open a new browser window and sign in to Power Apps Studio with your account details.
 
-2.  In the left pane, select **Apps**, select the **VanArdselApp** Power App, and then select **Edit.**
+2.  In the left pane, select **Apps**, select the **VanArdselApp** app, and then select **Edit.**
 
     ![Open the VanArsdel app](media/image60.png)
 
@@ -529,9 +529,9 @@ Maria has built two apps, but she wants to combine them into a single app. To do
 
 ## Adding a Home screen to the app
 
-The final stage is to add a **Home** screen to the Power App. The **Home** screen will enable the engineer to move between the different parts of the app (inventory management, knowledge base, and appointments).
+The final stage is to add a **Home** screen to the app. The **Home** screen will enable the engineer to move between the different parts of the app (inventory management, knowledge base, and appointments).
 
-1.  In the **VanArsdelApp** Power App, in the toolbar, select **New screen**, and then select **Blank**.
+1.  In the **VanArsdelApp** app, in the toolbar, select **New screen**, and then select **Blank**.
 
 2.  In the **Tree view** pane, change the name of the screen (**Screen2**) to **Home**.
 
@@ -626,7 +626,7 @@ Finally, you can test the app.
 
 1.  On the **File** menu, on the **Save** tab, enter the text **Complete version with Home screen** in the **Version note** box, and select **Save**.
 
-2.  Select the back arrow icon to return to the **Home** screen and press **F5** to run the Power App.
+2.  Select the back arrow icon to return to the **Home** screen and press **F5** to run the app.
 
 3.  Verify that the **Home** screen for the app appears.
 

powerapps-docs/guidance/fusion-dev-ebook/04-using-dataverse-as-data-source.md

@@ -40,7 +40,7 @@ Dataverse contains a collection of open-sourced, standardized, extensible data e
 In Dataverse, each entity is tabular, with a default set of columns also defined by the Open Data Initiative. You can view the definition of a table using the *Edit* command for that entity in the list of tables. You can extend a table with your own columns, but as before, it's good practice to use existing columns wherever possible. The example below shows the default definition of the *Account* table.
 
 > [!NOTE]
-> You can modify the display name of tables and columns without changing their names. The display names are the default labels that appear on forms in a Power App.
+> You can modify the display name of tables and columns without changing their names. The display names are the default labels that appear on forms in Power Apps.
 
 ![The Account table in Dataverse](media/image77.png)
 

powerapps-docs/guidance/fusion-dev-ebook/05-creating-publishing-web-api-in-azure.md

@@ -38,11 +38,11 @@ The knowledge base part of the app currently just contains a placeholder **Brows
 -   When all matching tips have been found, the technician can select a tip to view its details.
 -   A technician can also add new tips to the knowledge base, as well as add notes and comments to existing tips.
 
-    The knowledge base is large and growing, and querying across multiple tables and columns can involve complex logic that requires significant compute power. To reduce the load on the Web API, Kiana decides to use Azure Search to provide the search functionality, as described earlier. To support the Power App, Kiana decides that the following operations are required from the Web API:
+    The knowledge base is large and growing, and querying across multiple tables and columns can involve complex logic that requires significant compute power. To reduce the load on the Web API, Kiana decides to use Azure Search to provide the search functionality, as described earlier. To support the app, Kiana decides that the following operations are required from the Web API:
 
 -   Find the details of a specified knowledge base tip from the **Tips** table.
 -   Update an existing knowledge base tip in the **Tips** table.
--   Add a new knowledge base tip to the **Tips** table, which might also involve adding rows to the **BoilerParts** and **Engineers** tables if the specified part or engineer currently have no tips recorded against them. The routine that actually performs the logic behind adding a new tip will be implemented as an Azure Logic app called from the Power Apps app.
+-   Add a new knowledge base tip to the **Tips** table, which might also involve adding rows to the **BoilerParts** and **Engineers** tables if the specified part or engineer currently have no tips recorded against them. The routine that actually performs the logic behind adding a new tip will be implemented as an Azure Logic app called from Power Apps.
 
 ## Defining the Web API operations: Field scheduling
 
@@ -55,7 +55,7 @@ Scheduling technician appointments requires not only querying, adding, and remov
 > [!NOTE]
 > The database actually contains a fourth table named **AppointmentsStatus**. This table contains a list of valid appointment statuses and is simply a lookup used by other parts of the existing appointments system.
 
-Kiana decides that the following operations would be useful for the Field Scheduling part of the Power App:
+Kiana decides that the following operations would be useful for the Field Scheduling part of the app:
 
 -   Find all appointments for a specified technician.
 -   Find all appointments for the current day for a specified technician.
@@ -1055,7 +1055,7 @@ To create the Web API operations for the Field Scheduling part of the system, Ki
 
 13. When deployment is complete, browse to the website but change the URL in the browser to **https://*\<webapp name\>*.azurewebsites.net/swagger**. Verify that the operations for the **Appointments**, **Customer**, and **ScheduleEngineer** controllers are now available.
 
-The Web API is now ready to be incorporated into the Power App.
+The Web API is now ready to be incorporated into the app.
 
 > [!div class="step-by-step"]
 > [Previous](04-using-dataverse-as-data-source.md)

powerapps-docs/guidance/fusion-dev-ebook/06-using-web-api-in-app.md

@@ -232,7 +232,7 @@ Now that the connection has been added to the app, Maria can modify the screens
 
 15. Change the **Default** property of the **Image\_DataCard1** control to **ThisItem.imageUrl**.
 
-16. In the left pane, on the **Data** tab, right-click the **Table1** data connection, and then select **Remove** to delete it from the Power App. This connection is no longer required.
+16. In the left pane, on the **Data** tab, right-click the **Table1** data connection, and then select **Remove** to delete it from the app. This connection is no longer required.
 
     ![Remove the Table1 connection](media/image127.png)
 
@@ -369,7 +369,7 @@ This formula displays the time element of the **startDateTime** field.
     Navigate(AppointmentDetails, ScreenTransition.None);
     ```
 
-22. In the left pane, on the **Data** tab, right-click the **Appointments** data connection, and then select **Remove** to delete it from the Power App.
+22. In the left pane, on the **Data** tab, right-click the **Appointments** data connection, and then select **Remove** to delete it from the app.
 
 23. Save the app.
 
@@ -536,7 +536,7 @@ Kiana can now create a custom connector that Power Apps uses to send search requ
 
 ## Updating the app to use Azure Cognitive Search: Field Knowledgebase
 
-Maria can now use the custom connector in the Power App. But first, she requires a key that grants her the privileges required to connect to the Azure Cognitive Search service. Preeti obtains the key from the **Keys** page for the service in the Azure portal, and gives it to Maria:
+Maria can now use the custom connector in the app. But first, she requires a key that grants her the privileges required to connect to the Azure Cognitive Search service. Preeti obtains the key from the **Keys** page for the service in the Azure portal, and gives it to Maria:
 
 ![Search Service key in the Azure portal](media/image154.png)
 
@@ -590,7 +590,7 @@ Maria edits the app in Power Apps Studio and performs the following tasks:
 
 12. Close the preview window and return to Power Apps Studio.
 
-13. In the **Tree view** pane, right-click the **PartDetails** screen, and select **Duplicate screen**. This action will add another screen to the Power App, named **PartDetails\_1**:
+13. In the **Tree view** pane, right-click the **PartDetails** screen, and select **Duplicate screen**. This action will add another screen to the app, named **PartDetails\_1**:
 
     ![Duplicate the PartDetails screen](media/image159.png)