/topics/admin.md has outdated info

[stockholmux]

In reviewing /topics/admin.md for #91, I noticed the following things:

1. References to testing in FreeBSD / OpenBSD / OS X; to my knowledge this testing hasn't be done for Valkey.
2. Antirez's blog is references for "this attack". I think the attack in question really only relevant to Redis 3.2 or below.
3. Under the section "Running Valkey on EC2" it says "Do not use old instance families. For example, use m3.medium with HVM instead of m1.medium with PV." m3 is now a previous generation instance.
4. It says CONFIG SET slave-read-only no

[zuiderkwast]

References to testing in FreeBSD / OpenBSD / OS X; to my knowledge this testing hasn't be done for Valkey.

We have FreeBSD and macOS in our Daily CI.

For the other BSDs in the list, to which we can add NetBSD and DragonFlyBSD, we have had several contributions, so I'm pretty sure we have at least one person that has tested them:

• Support pipe2() on *BSD valkey#462
• Use kqueue as the backend of AE on DragonFlyBSD valkey#450
• Detect accept4() on specific versions of various platforms valkey#294
• Use SOCK_NONBLOCK to reduce system calls for outgoing connections valkey#293 (This one also touches Solaris and Illumos)

Antirez's blog is references for "this attack". I think the attack in question really only relevant to Redis 3.2 or below.

Deleting these sentences.

Under the section "Running Valkey on EC2" it says "Do not use old instance families. For example, use m3.medium with HVM instead of m1.medium with PV." m3 is now a previous generation instance.

Deleting this bullet.

It says CONFIG SET slave-read-only no

Already fixed in some other PR.