Reviewed/accepted editor's changes

Author: KumarVivek

powerapps-docs/guidance/fusion-dev-ebook/01-what-is-fusion-dev-approach.md

@@ -14,7 +14,7 @@ ms.reviewer: kvivek
 # Chapter 1: What is the fusion development approach? 
 
 Effective application development depends on accurate and efficient communication of business requirements, and ideas for addressing these requirements. Many software engineering strategies promote the concept of the users of applications being highly involved throughout the lifetime of the development process. However, there's frequently a "glass wall" between the users and the software creators. Both parties can see each other and talk through their perspectives of how a new system should work, but the terminology used by one party might not be understood by the other. The need to translate language and ideas into a grammar that all members involved in the development process can agree on is fundamental to success. Additionally, in a rapidly changing business environment, time is of the essence. Failure to be agile enough to exploit a narrow window of opportunity can be costly. By using Power Apps, you can create and deploy working solutions that meet users' needs very quickly.
-<!--note from editor: This image needs better alt text.-->
+
 ![Basic app created with Power Apps](media/image1.png)
 
 Power Apps enables a business user to quickly innovate and experiment with ways to improve their business processes. Using Power Apps, "citizen developers" who understand the business requirements can quickly put together the basics of a solution, with a minimum of coding effort. A citizen developer uses the graphical tooling provided by Power Apps Studio to create the business user's interface to a new system and some elemental logic that describes the functionality&mdash;typically involving data entry forms, displays, and reports. It's relatively easy to generate a working app from the data connectors that are supplied with Power Apps. These connectors enable the user interface to connect to many data sources, such as SQL Server, SharePoint, Oracle, Excel, Twitter, Dynamics, and several hundred others.
@@ -23,11 +23,11 @@ Power Apps enables a business user to quickly innovate and experiment with ways
 > For a full list of connectors, go to [Connectors reference](/connectors/connector-reference/).
 
 Many apps built like this can fulfill an immediate business need quickly and cheaply, but there will always be more complex situations that can't be satisfied in this way. For example, your organization might have existing systems and databases with which the app needs to interact, and for which no connector is currently available. There might be additional business logic that needs to be enforced to ensure that data remains consistent. An app might need to implement a complex, dynamic business flow. This is where professional developers come into play. After a citizen developer has produced the front-end prototype for a system, the professional developer can work with them to create any appropriate custom connectors that they might require. A custom connector doesn't just provide a path to a data source; a professional developer can create custom connectors that give access to other services, such as Azure Logic Apps, which in turn can invoke Azure Functions. Connectors such as these enable the citizen developer to incorporate complex business logic into their apps without requiring that they understand how it's implemented.
-<!--note from editor: This image needs better alt text.-->
+
 ![App with custom connector](media/image2.png)
 
 A common use case for a custom connector is to enable an app to access other systems and services inside and outside of an organization. A professional developer can create a Web API that wraps the operations exposed by these systems and services, host the Web API as a web app, and then make this web app available to a custom connector through Azure API Management.
-<!--note from editor: This image needs better alt text.-->
+
 ![Web API with custom connector](media/image3.png)
 
 > [!NOTE]
@@ -37,7 +37,7 @@ Fusion development with Power Apps is about combining the worlds of the citizen
 
 > [!NOTE]
 > Gartner describes *digital fusion teams* as "distributed and multidisciplinary digital business teams that blend technology and other types of ___domain expertise. At least 84% of companies and 59% of government entities have fusion teams." (Source: 2019 Gartner Digital Business Teams Survey)
-<!--note from editor: This image needs better alt text.-->
+
 ![Fusion development process](media/image4.png)
 
 For a detailed introduction to the fusion development process and how it can accelerate development times, go to [Citizen developers use Microsoft Power Apps to build an intelligent launch assistant](https://aka.ms/AAbvfzj).

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

@@ -5,7 +5,7 @@ author: spboyer
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: ebook
-ms.date: 04/21/2021
+ms.date: 04/26/2021
 ms.author: shboyer
 ms.reviewer: kvivek
 
@@ -26,7 +26,7 @@ When a technician arrives at a customer's home and finds they don't have a part
 -   Because mistakes do happen, the office inventory manager must audit the workbook against the inventory.
 
 A solution is to create an 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, which 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.
-<!--note from editor: This image needs better alt text.-->
+
 ![Field Inventory Management app](media/image5.png)
 
 ## Field knowledge base
@@ -40,7 +40,7 @@ It's impossible for one single technician to know everything about every model o
 - Knowledge is a subject that ebbs and flows with technician turnover. Important information can be easily lost or misremembered unless it's recorded.
 
 A solution is to capture information about furnaces and air conditioners&mdash;problems that have occurred, and how they were fixed&mdash;in a knowledge base. A technician can use an app to record comments about a job and the repairs performed while still at the customer's premises. The same app can provide an interface that allows the technician to query the knowledge base about any useful information that other technicians might have learned from similar jobs. The knowledge base itself can be implemented as a database with Azure Cognitive Search providing the lookup facility, based on one or more keywords.
-<!--note from editor: This image needs better alt text.-->
+
 ![Field knowledge base app](media/image6.png)
 
 ## Field scheduling and notes
@@ -60,7 +60,7 @@ There are several obvious drawbacks to the current scheduling strategy:
 - The technician spends a lot of time at the end of the day updating customer notes, when they would rather go home.
 
 VanArsdel can use an app that acts as a front end to the legacy system. It would enable the office receptionist 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 appointment schedule in real time so they can 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.
-<!--note from editor: This image needs better alt text.-->
+
 ![Field scheduling app](media/image7.png)
 
 ## Fusion development team members