Clarified monitoring of job database

Author: dimitri-furman

articles/sql-database/sql-database-job-automation-overview.md

@@ -199,7 +199,7 @@ For the current preview, an existing Azure SQL database (S0 or higher) is requir
 
 The *Job database* doesn't literally need to be new, but should be a clean, empty, S0 or higher service objective. The recommended service objective of the *Job database* is S1 or higher, but the optimal choice depends on the performance needs of your job(s): the number of job steps, the number of job targets, and how frequently jobs are run. For example, an S0 database might be sufficient for a job agent that runs few jobs an hour targeting less than ten databases, but running a job every minute might not be fast enough with an S0 database, and a higher service tier might be better. 
 
-If operations against the job database are slower than expected, [monitor](sql-database-monitor-tune-overview.md#monitor-database-performance) database performance and resource utilization during periods of slowness using Azure portal or the [sys.dm_db_resource_stats](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database) DMV. If utilization of a resource, such as CPU, Data IO, or Log Write approaches 100% and correlates with periods of slowness, consider incrementally scaling the database to higher service objectives (either in the [DTU model](sql-database-service-tiers-dtu.md) or in the [vCore model](sql-database-service-tiers-vcore.md)) until job database performance is sufficiently improved.
+If operations against the job database are slower than expected, [monitor](sql-database-monitor-tune-overview.md#monitor-database-performance) database performance and the resource utilization in the job database during periods of slowness using Azure portal or the [sys.dm_db_resource_stats](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database) DMV. If utilization of a resource, such as CPU, Data IO, or Log Write approaches 100% and correlates with periods of slowness, consider incrementally scaling the database to higher service objectives (either in the [DTU model](sql-database-service-tiers-dtu.md) or in the [vCore model](sql-database-service-tiers-vcore.md)) until job database performance is sufficiently improved.
 
 
 ##### Job database permissions