Fixed links

Author: dimitri-furman

articles/azure-sql/database/file-space-manage.md

@@ -112,7 +112,7 @@ Understanding the following storage space quantities are important for managing
 |**Data max size**|The maximum amount of data space that can be used by the elastic pool for all of its databases.|The space allocated for the elastic pool should not exceed the elastic pool max size.  If this condition occurs, then space allocated that is unused can be reclaimed by shrinking database data files.|
 
 > [!NOTE]
-> The error message "The elastic pool has reached its storage limit" indicates that the database objects have been allocated enough space to meet the elastic pool storage limit, but there may be unused space in the data space allocation. Consider increasing the elastic pool's storage limit, or as a short-term solution, freeing up data space using the [Reclaim unused allocated space](#reclaim-unused-allocated-space) section below. You should also be aware of the potential negative performance impact of shrinking database files, see [Index maintenance after shrink](#index-maintenance-after-shrink) section below.
+> The error message "The elastic pool has reached its storage limit" indicates that the database objects have been allocated enough space to meet the elastic pool storage limit, but there may be unused space in the data space allocation. Consider increasing the elastic pool's storage limit, or as a short-term solution, freeing up data space using the [Reclaim unused allocated space](#reclaim-unused-allocated-space) section below. You should also be aware of the potential negative performance impact of shrinking database files, see [Index maintenance after shrink](#rebuild-indexes) section below.
 
 ## Query an elastic pool for storage space information
 
@@ -195,7 +195,7 @@ ORDER BY end_time DESC;
 > [!IMPORTANT]
 > Shrink commands impact database performance while running, and if possible should be run during periods of low usage.
 
-### <a name="#shrinking-data-files"></a>Shrink data files
+### <a name="shrinking-data-files"></a>Shrink data files
 
 Because of a potential impact to database performance, Azure SQL Database does not automatically shrink data files. However, customers may shrink data files via self-service at a time of their choosing. This should not be a regularly scheduled operation, but rather, a one-time event in response to a major reduction in data file used space consumption.
 
@@ -241,7 +241,7 @@ DBCC SHRINKFILE ('data_0', TRUNCATEONLY);
 GO
 ```
 
-Be aware of the potential negative performance impact of shrinking database files, see the [Index maintenance after shrink](#index-maintenance-after-shrink) section below. 
+Be aware of the potential negative performance impact of shrinking database files, see the [Index maintenance after shrink](#rebuild-indexes) section below. 
 
 ### Shrinking transaction log file