Apply suggestions from code review

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Reshma Abdul Rahim <61033581+Reshrahim@users.noreply.github.com>

Author: Reshrahim

Data/neo4jDatabases/README.md

@@ -17,6 +17,7 @@ Developer documentation is embedded in the resource type definition YAML file, a
 Properties for the **Radius.Data/neo4jDatabases** resource type are provided via the [Recipe Context](https://docs.radapp.io/reference/context-schema/) object. These properties include:
 
 - `context.resource.properties.secretName` (string, required): Name of the secret containing the database credentials. The secret must have `USERNAME` and `PASSWORD` keys.
+- `context.resource.properties.database` (string, optional): Name of the database to create/use. Defaults to the resource name.
 
 ## Recipe Output Properties
 

Data/neo4jDatabases/neo4jDatabases.yaml

@@ -43,7 +43,6 @@ types:
       When deploying the application definition, provide the database password value as a parameter. It is recommended to use a password generator such as `openssl` or equivalent. For example, `rad deploy app.bicep -p password=$(openssl rand -hex 16)`.
 
       To connect your container to the database, create a connection from the Container resource to the database as shown below.
-      ```
       To connect to the new Neo4j database, add a connection between the container and the new Neo4j database. The final Container resource should look similar to:
       ```
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {