rename allocating-fips to managing-fips, fix links

topics/compute/openstack/docs/additional-information/virtual-networking.md

@@ -18,7 +18,7 @@ Prerequisites:
 In How-to guides we have prepared several scenarios:
 
 - [Accessing instances](../how-to-guides/accessing-instances.md)
-- [Allocating floating IPs](../how-to-guides/allocating-floating-ips.md)
+- [Allocating floating IPs](../how-to-guides/managing-floating-ips.md)
 - [Create networking](../how-to-guides/create-networking.md)
 - [High Availability deployment](../how-to-guides/high-availability-deployment.md)
 

topics/compute/openstack/docs/getting-started/creating-first-infrastructure.md

@@ -160,7 +160,7 @@ __6.__ In **Key Pair** select the key that was created in section [Create Key Pa
     ![](/compute/openstack/images/instance/instance6.png)
 
 __9.__ Wait until instance initialization finishes and
-[Associate Floating IP](../how-to-guides/allocating-floating-ips.md#allocation-and-assignment-of-fip).
+[Associate Floating IP](../how-to-guides/managing-floating-ips.md).
 For group project always select the same network as used in
 [Router gateway](../how-to-guides/create-networking.md#router-creation).
 

topics/compute/openstack/docs/how-to-guides/accessing-instances.md

@@ -15,7 +15,7 @@ Before you can access instances running on OpenStack, you should have met the fo
 - [Configured Security groups](../getting-started/creating-first-infrastructure.md#update-security-group): You should have configured security groups in OpenStack to allow traffic to and from your instances.
 - [Imported SSH key](../getting-started/creating-first-infrastructure.md#create-key-pair): If you plan to access instances, you should have imported an SSH key into OpenStack that you can use to authenticate with your instances.
 - [Created Virtual machine](../getting-started/creating-first-infrastructure.md#create-virtual-machine-instance): You should have created a virtual machine instance in OpenStack that you want to access.
-- [Associated Floating IP](../how-to-guides/allocating-floating-ips.md): If you plan to access instances from outside the OpenStack environment, you should have associated a floating IP with your instance.
+- [Associated Floating IP](../how-to-guides/managing-floating-ips.md): If you plan to access instances from outside the OpenStack environment, you should have associated a floating IP with your instance.
 
 If you're unsure about any of these prerequisites, please refer to the relevant documentation page for more information.
 
@@ -28,7 +28,7 @@ There are several different methods that you can use to access instances running
 
 Consult the relevant documentation for each access method for more detailed instructions on how to set up and use each method.
 
-## Connecting to Instances
+## Connecting To Instances
 To connect to instances running on OpenStack, you can use one of the available access methods, such as SSH, remote desktop, or VNC. Here are step-by-step instructions on how to connect to your instances using each method:
 === "Linux"
 

topics/compute/openstack/docs/how-to-guides/create-router.md

@@ -111,6 +111,6 @@ If you have no gateway on you router, you can assign a new one.
     openstack router unset --external-gateway my-router1
     ```
 
-    Make sure to first [release FIPs](../how-to-guides/allocating-floating-ips.md#release-of-floating-ip) from the network.
+    Make sure to first [release FIPs](../how-to-guides/managing-floating-ips.md#releasing-floating-ip) from the network.
 
     Additional router configuration is available in [official CLI documentation](https://docs.openstack.org/python-openstackclient/train/cli/command-objects/router.html).

topics/compute/openstack/docs/how-to-guides/allocating-floating-ips.md → topics/compute/openstack/docs/how-to-guides/managing-floating-ips.md

 ---
 
-title: Allocating Floating IPs
+title: Managing Floating IPs
 search:
   exclude: false
 ---
 
-# Allocating Floating IPs
+# Managing Floating IPs
 In OpenStack, a floating IP address is a public IP address that can be assigned to an instance. This allows external access to the instance, even if it is behind a router or firewall. In this how-to guide, we will walk you through the process of allocating, assigning, disassociating, and releasing a floating IP address.
 
 ## Prerequisites

topics/compute/openstack/docs/technical-reference/brno-site/networking.md

@@ -15,7 +15,7 @@ It is currently limited to the common internal networks. You can start your mach
 
 ### IPv4 Group Floating IPs
 
-The situation is rather different for group projects. You cannot use the same approach as for personal projects. You should create a virtual network as described on page [Create networking](../../how-to-guides/create-networking.md) instead and select one of the pools with `-GROUP` suffix as show on page [Allocating floating IPs](../../how-to-guides/allocating-floating-ips.md). Namely:
+The situation is rather different for group projects. You cannot use the same approach as for personal projects. You should create a virtual network as described on page [Create networking](../../how-to-guides/create-networking.md) instead and select one of the pools with `-GROUP` suffix as show on page [Allocating floating IPs](../../how-to-guides/managing-floating-ips.md). Namely:
 
  - `public-cesnet-78-128-251-GROUP`
  - `public-cesnet-195-113-167-GROUP`

topics/compute/openstack/mkdocs.yml

@@ -8,7 +8,7 @@ nav:
     - getting-started/creating-first-infrastructure.md
   - How-to guides:
     - how-to-guides/accessing-instances.md
-    - how-to-guides/allocating-floating-ips.md
+    - how-to-guides/managing-floating-ips.md
     - how-to-guides/attaching-interface.md
     # - how-to-guides/attaching-remote-storage.md
     - how-to-guides/changing-vm-resources.md