Fix numbering and remove the optional section

Author: ggailey777

articles/azure-functions/create-first-function-cli-python.md

@@ -43,36 +43,6 @@ Before you begin, you must have the following requirements in place:
 
 [!INCLUDE [functions-x86-emulation-on-arm64-note](../../includes/functions-x86-emulation-on-arm64-note.md)]
 
-### Prerequisite check
-
-Verify your prerequisites, which depend on whether you're using Azure CLI or Azure PowerShell for creating Azure resources.
-
-# [Azure CLI](#tab/azure-cli)
-
-::: zone pivot="python-mode-configuration"
-+ In a terminal or command window, run `func --version` to check that the Azure Functions Core Tools version is 4.x.
-::: zone-end
-::: zone pivot="python-mode-decorators"
-+ In a terminal or command window, run `func --version` to check that the Azure Functions Core Tools version is 4.0.4785 or later.
-::: zone-end
-+ Run `az --version` to check that the Azure CLI version is 2.4 or later.
-
-+ Run `az login` to sign in to Azure and verify an active subscription.
-
-+ Run `python --version` (Linux/macOS) or `py --version` (Windows) to check your Python version reports 3.9.x, 3.8.x, or 3.7.x.
-
-# [Azure PowerShell](#tab/azure-powershell)
-
-+ In a terminal or command window, run `func --version` to check that the Azure Functions Core Tools version is 4.x.
-
-+ Run `(Get-Module -ListAvailable Az).Version` and verify version 5.0 or later.
-
-+ Run `Connect-AzAccount` to sign in to Azure and verify an active subscription.
-
-+ Run `python --version` (Linux/macOS) or `py --version` (Windows) to check your Python version reports 3.9.x, 3.8.x, or 3.7.x.
-
----
-
 ## <a name="create-venv"></a>Create and activate a virtual environment
 
 In a suitable folder, run the following commands to create and activate a virtual environment named `.venv`. Make sure that you're using Python 3.9, 3.8, or 3.7, which are supported by Azure Functions.
@@ -143,14 +113,9 @@ In Azure Functions, a function project is a container for one or more individual
     ```
 
     `func new` creates a subfolder matching the function name that contains a code file appropriate to the project's chosen language and a configuration file named *function.json*.
-
-    Get the list of templates by using the following command:
-
-    ```console
-    func templates list -l python
-    ```
-::: zone-end
-::: zone pivot="python-mode-decorators"
+    ```  
+::: zone-end  
+::: zone pivot="python-mode-decorators"  
 1. Run the `func init` command as follows to create a functions project in a folder named *LocalFunctionProj* with the specified runtime and the specified programming model version.
 
     ```console
@@ -162,21 +127,22 @@ In Azure Functions, a function project is a container for one or more individual
     ```console
     cd LocalFunctionProj
     ```
-
+    
     This folder contains various files for the project, including configuration files named [*local.settings.json*](functions-develop-local.md#local-settings-file) and [*host.json*](functions-host-json.md). Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
 
 1. The file `function_app.py` can include all functions within your project. To start with, there's already an HTTP function stored in the file.
 
-  ```python
-  import azure.functions as func
+   ```python
+   import azure.functions as func
   
-  app = func.FunctionApp()
+   app = func.FunctionApp()
   
-  @app.function_name(name="HttpTrigger1")
-  @app.route(route="hello")
-  def test_function(req: func.HttpRequest) -> func.HttpResponse:
-      return func.HttpResponse("HttpTrigger1 function processed a request!")
-  ```
+   @app.function_name(name="HttpTrigger1")
+   @app.route(route="hello")
+   def test_function(req: func.HttpRequest) -> func.HttpResponse:
+       return func.HttpResponse("HttpTrigger1 function processed a request!")
+   ```
+   
 1. Open the local.settings.json project file and verify that the `AzureWebJobsFeatureFlags` setting has a value of `EnableWorkerIndexing`. This is required for Functions to interpret your project correctly as the Python v2 model. You'll add this same setting to your application settings after you publish your project to Azure. 
 
 1. In the local.settings.json file, update the `AzureWebJobsStorage` setting as in the following example:
@@ -185,37 +151,9 @@ In Azure Functions, a function project is a container for one or more individual
     "AzureWebJobsStorage": "UseDevelopmentStorage=true",
     ```
 
-    This tells the local Functions host to use the storage emulator for the storage connection currently required by the Python v2 model. When you publish your project to Azure, you'll need to instead use the default storage account. If you're instead using an Azure Storage account, set your storage account connection string here.
-::: zone-end
-
-### (Optional) Examine the file contents
-
-If desired, you can skip to [Run the function locally](#run-the-function-locally) and examine the file contents later.
-
-::: zone pivot="python-mode-configuration"
-#### \_\_init\_\_.py
-
-*\_\_init\_\_.py* contains a `main()` Python function that's triggered according to the configuration in *function.json*.
-
-:::code language="python" source="~/functions-quickstart-templates/Functions.Templates/Templates/HttpTrigger-Python/__init__.py":::
-
-For an HTTP trigger, the function receives request data in the variable `req` as defined in *function.json*. `req` is an instance of the [azure.functions.HttpRequest class](/python/api/azure-functions/azure.functions.httprequest). The return object, defined as `$return` in *function.json*, is an instance of [azure.functions.HttpResponse class](/python/api/azure-functions/azure.functions.httpresponse). For more information, see [Azure Functions HTTP triggers and bindings](./functions-bindings-http-webhook.md?tabs=python).
-
-#### function.json
-
-*function.json* is a configuration file that defines the input and output `bindings` for the function, including the trigger type.
-
-If desired, you can change `scriptFile` to invoke a different Python file.
-
-:::code language="json" source="~/functions-quickstart-templates/Functions.Templates/Templates/HttpTrigger-Python/function.json":::
-
-Each binding requires a direction, a type, and a unique name. The HTTP trigger has an input binding of type [`httpTrigger`](functions-bindings-http-webhook-trigger.md) and output binding of type [`http`](functions-bindings-http-webhook-output.md).
-::: zone-end
-::: zone pivot="python-mode-decorators"
-`function_app.py` is the entry point to the function and where functions will be stored and/or referenced. This file will include configuration of triggers and bindings through decorators, and the function content itself. 
-
-For more information, see [Azure Functions HTTP triggers and bindings](./functions-bindings-http-webhook.md?tabs=python).
-
+    This tells the local Functions host to use the storage emulator for the storage connection currently required by the Python v2 model. When you publish your project to Azure, you'll need to instead use the default storage account. If you're instead using an Azure Storage account, set your storage account connection string here.   
+::: zone-end  
+::: zone pivot="python-mode-decorators"  
 ## Start the storage emulator
 
 By default, local development uses the Azurite storage emulator. This emulator is used when the `AzureWebJobsStorage` setting in the *local.settings.json* project file is set to `UseDevelopmentStorage=true`. When using the emulator, you must start the local Azurite storage emulator before running the function.